You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't stop learning until we win. In Round 10 Haywire placed 9th.
Summary
I had the privilege to gain access to the Techempower environment and benchmark Haywire using the same parameters that Round 11 was run with. ulib is the winner of round 11 so I compared Haywire's experimental picohttpparser branch that includes the new HTTP parser with syscall response batching. This is not polished but it is an experimental branch to see how these changes compete.
The machine benchmarked against has 20 physical cores and 20 hyper-threaded cores. I tested Haywire in 20 and 40 thread configurations to see how this changes performance.
Win Techempower benchmarks
Don't stop learning until we win. In Round 10 Haywire placed
9th
.Summary
I had the privilege to gain access to the Techempower environment and benchmark Haywire using the same parameters that
Round 11
was run with.ulib
is the winner of round 11 so I compared Haywire's experimentalpicohttpparser
branch that includes the new HTTP parser with syscall response batching. This is not polished but it is an experimental branch to see how these changes compete.The machine benchmarked against has
20
physical cores and20
hyper-threaded cores. I tested Haywire in 20 and 40 thread configurations to see how this changes performance.Concurrency: 256
ulib
Haywire (20 threads)
Haywire (40 threads)
Concurrency: 1024
ulib
Haywire (20 threads)
Haywire (40 threads)
Concurrency: 4096
ulib
Haywire (20 threads)
Haywire (40 threads)
Concurrency: 16384
ulib
Haywire (20 threads)
Haywire (40 threads)
The text was updated successfully, but these errors were encountered: