← ClaudeAtlas

ghz-loadlisted

Use when a gRPC service needs load testing or a latency regression gate: ghz runs with request count, concurrency, rate and duration, JSON, CSV or HTML output, and p50, p95 and p99 latency, RPS and error rates checked in CI.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# ghz-load ## Overview Per [ghz.sh/docs/usage](https://ghz.sh/docs/usage), ghz accepts a `.proto` (or compiled `protoset`), a method, a host:port, and load parameters, and emits per-request metrics + a summary. This skill wraps ghz for two use cases: ad-hoc throughput measurement and CI regression gating. ## When to use - New gRPC service - what's the throughput ceiling? - Suspected latency regression - quantify before / after a change. - CI gate: each PR runs a short ghz pass and fails if p99 exceeds the previous baseline. - Capacity planning - at what concurrency does the service hit its CPU/memory ceiling? ## Authoring ### Install Per [ghz.sh/docs/install](https://ghz.sh/docs/install): ```bash # Homebrew brew install ghz # Go install go install github.com/bojand/ghz/cmd/ghz@latest ``` Verify: ```bash ghz --version ``` ### Configure a `config.json` Per ghz docs, `--config=path` reads a JSON / TOML config. For reproducibility, commit it to the repo: ```json { "proto": "./proto/user.proto", "import-paths": ["./proto", "./vendor"], "call": "user.v1.UserService/GetUser", "host": "localhost:8080", "insecure": true, "total": 10000, "concurrency": 50, "rps": 0, "data": { "id": "user-1" }, "format": "json", "output": "ghz-report.json", "skipFirst": 100 } ``` `skipFirst: 100` discards the first 100 requests (cold-cache / warmup). Set per-service. ## Running ### Basic load test ```bash ghz --proto=./proto/user.proto \ --call=u