Update roadrunner to v0.8.0 - #945
Conversation
|
/benchmark -f roadrunner |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
/benchmark -f roadrunner |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
/benchmark -f roadrunner |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
/benchmark -f roadrunner --save |
|
👋 |
|
|
70aaed7 to
753b760
Compare
|
/benchmark -f roadrunner --save |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
@MDA2AV PR is mergeable |
|
|
||
| %% Cache stores the already-encoded JSON body, so a cache hit ships the | ||
| %% bytes verbatim instead of re-encoding the item map every request; | ||
| %% `roadrunner_resp:body/4` folds in the `x-cache` marker in one call. |
There was a problem hiding this comment.
Where is 200ms TTL being evaluated?
There was a problem hiding this comment.
Good catch. You are right, I missed it. Thanks for checking it out. I'll revisit the spec to ensure code is 100% aligned with it.
This branch saved results before MDA2AV#1034, so it carries 38 site/data/<profile>-<conns>.json files that main has since replaced with one file per framework; git reported them all as modify/delete conflicts. Every row this PR re-measured for the v0.8.0 bump was re-applied to site/data/results/roadrunner.json and the flat files dropped. All 38 keys already existed, so all 38 are updates rather than additions - for example baseline-512 833,311 -> 919,625 rps and async-db-1024 84,434 -> 134,059 rps. Only rows this PR touched moved across, so nothing main has changed since is resurrected.
Description
Updates roadrunner from v0.6.0 to v0.8.0 and tunes the adapter for the high-concurrency profiles: raises the listener connection limits, runs the database queries as prepared statements, and scopes response compression to the routes that serve compressible content.
PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> --saveAlways specify
-f <framework>. Results are automatically compared against the current leaderboard.Run benchmarks locally
You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.
Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk, ghz) are built as self-contained Docker images on first run.