Gobenchdata is a tool for inspecting golang benchmark outputs.
SurgeMQ is a high performance MQTT broker and client library that aims to be fully compliant with MQTT 3.1 and 3.1.1 specs. The primary package that's of interest is package service. It provides the MQTT Server and Client services in a library form. Current performance benchmark of SurgeMQ, running all publishers, subscribers and broker on a single 4-core (2.8Ghz i7) MacBook Pro, is able to achieve: In addition, SurgeMQ has been tested with the following client libraries and it _seems_ to work: A quick example of how to use SurgeMQ:
Command benchgate benchmarks a head source tree against a base tree on one machine and fails on a confirmed regression.
Package benchgate benchmarks a head source tree against a base tree on one machine and finds confirmed regressions.
Command interleave runs the Go FromBools/ToBools benchmarks and the NumPy reference (bench/numpy_bools.py) in alternating rounds on one core, and prints the median GB/s of each cell with the 1-minute load seen around the rounds that were kept.
Package load_generator drives memstash caches under continuous, verified load.
Command benchgate fails your CI when a benchmark regresses: it compares two `go test -bench` result files and exits 1 when a benchmark got slower beyond a threshold with statistical significance.
Package compare benchmarks modernc.org/jit/wasm against wazero, in a module of its own so that modernc.org/jit/wasm does not depend on wazero.
Package middleware contains the middleware benchmarks that live outside the component modules, so the plugin and aggregate modules never depend on benchmark-only code.
Package rdma contains cross-host latency and bandwidth benchmarks for github.com/shibingli/ydx/rdma.
Package auth contains the authentication and authorization benchmarks that live outside the component module, so github.com/shibingli/ydx/auth never depends on benchmark-only code or comparison libraries.
Package sse contains the SSE benchmarks that live outside the component module, so github.com/shibingli/ydx/sse never depends on benchmark-only code.
Package template benchmarks template engines on one shared page workload and verifies that every engine produces the same HTML.
Package workflow contains benchmarks for github.com/shibingli/ydx/workflow.
Package router contains the router benchmarks that live outside the component module, so github.com/shibingli/ydx/router never depends on benchmark-only code.
Package waf contains the net/http performance and compatibility benchmarks for github.com/shibingli/ydx/waf against Coraza v3.
Package jwt contains the JWT benchmarks that live outside the component module, so github.com/shibingli/ydx/auth/token/jwt never depends on benchmark-only code or comparison libraries.
Package log contains the logging benchmarks that live outside the component module, so github.com/shibingli/ydx/log never depends on benchmark-only code or comparison libraries.
Package wal benchmarks the ydx WAL against tidwall/wal and rosedblabs/wal.
Package raft contains benchmarks comparing ydx/raft with etcd raft and hashicorp/raft under the same in-memory storage and transport conditions.
Package json contains the JSON benchmarks that live outside the component module, so github.com/shibingli/ydx/json never depends on benchmark-only code or comparison libraries.