Skip to content

Commit 9946563

Browse files
docs: document noisy profile 4xx behavior in README
The noisy benchmark profile intentionally targets non-existent routes, producing 30-50% 4xx responses. This is expected — the server correctly returns 404 for unknown routes. Document this to avoid confusion when reviewing benchmark results.
1 parent 3657bab commit 9946563

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

frameworks/blitz/README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -725,6 +725,14 @@ zig build test
725725

726726
blitz is built to compete in [HttpArena](https://github.com/MDA2AV/HttpArena) benchmarks. See `meta.json` for the benchmark configuration.
727727

728+
### Noisy profile 4xx responses
729+
730+
The noisy benchmark profile uses 5 request templates, some of which intentionally target non-existent routes. This means 30–50% of responses will be 4xx (404) — this is **expected behavior**, not a bug. The server correctly returns 404 for unknown routes. The benchmark harness counts these as valid responses. Per-template breakdown:
731+
732+
- Templates 1–2: existing routes → ~100% 2xx
733+
- Templates 3–4: non-existent routes → ~100% 4xx (correct 404s)
734+
- Template 5: POST with body to a route that may time out at high concurrency
735+
728736
## License
729737

730738
MIT

0 commit comments

Comments
 (0)