Repository navigation
Conversation
|
/benchmark --save |
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Benchmark ResultsFramework:
Composite score, main against this run, in the board's default view:
The results on main were measured in another session, so a few points up or down can be the machine and not the change. Full log |
|
Thanks for the run. I've moved this PR to v1.15.1; as before, only What's new for the profiles since v1.13.1 is Tuntii/viltrum#119. The framework's own On my machine (4 workers), this takes the static profile from 6.4 to 2.1 syscalls per request. Over h2c it is +53% req/s; over TLS, AES-GCM takes most of the CPU, so the gain is smaller there.
Could you run |
|
👋 Benchmark request received. A collaborator will review and approve the run. |
|
|
|
Thanks for the run. I've moved this PR to v1.15.1; as before, only What's new for the profiles since v1.13.1 is Tuntii/viltrum#119. The framework's own On my machine (4 workers), this takes the static profile from 6.4 to 2.1 syscalls per request. Over h2c it is +53% req/s; over TLS, AES-GCM takes most of the CPU, so the gain is smaller there.
Could you run |
|
👋 Benchmark request received. A collaborator will review and approve the run. |
|
|
Moves the viltrum entry from v1.10.0 to v1.13.1. The entry's code is unchanged; only
VILTRUM_REFmoves.What changed in viltrum since v1.10.0:
scripts/validate.sh viltrumpasses: 98 passed, 0 failed, TLS verdict pass, opt-in tls_check pass.Could you run
/benchmark -f viltrumwhen you have a slot? Thanks.