4 ms·
How to run those benchmarks? At that Nim release page: https://nim-lang.org/blog/2021/10/19/version-160-released.html https://nim-lang.org/blog/2021/10/19/ver
by xet7 5y ago
How to run those benchmarks?
At that Nim release page:
https://nim-lang.org/blog/2021/10/19/version-160-released.html https://nim-lang.org/blog/2021/10/19/version-160-released.ht...
Is link to this benchmark:
https://web-frameworks-benchmark.netlify.app/result https://web-frameworks-benchmark.netlify.app/result
Where nim is 2nd with 200k req/s, but it is using httpbeast:
https://github.com/dom96/httpbeast https://github.com/dom96/httpbeast
That says it would be more useful to use jester:
https://github.com/dom96/jester https://github.com/dom96/jester
Jester has 150k req/s.
But, when looking at these:
https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/
drogon, actix etc has about 600k req/s .
Also redbean has about 600k req/s, when I tested:
https://redbean.dev/ https://redbean.dev/
I tested like this:
git clone https://github.com/wg/wrk.git https://github.com/wg/wrk.git
cd wrk
make
./wrk -H 'Accept-Encoding: gzip' -t 12 -c 120 http://127.0.0.1:8080/ http://127.0.0.1:8080/
When I tested https://caddyserver.com https://caddyserver.com v2, it did show about 800k req/s.
It would be very helpful to know how those benchmarks are actually done, so that I could compare what is actually fastest in real world, and not just use some for benchmark tested winning non-realistic code.
- sp33der89 5y agoThe source code for the benchmarks is here: https://github.com/the-benchmarker/web-frameworks https://github.com/the-benchmarker/web-frameworks And the httpbeast code is here: https://github.com/the-benchmarker/web-frameworks/tree/master/nim/httpbeast https://github.com/the-benchmarker/web-frameworks/tree/maste... TechEmpower and TheBenchmarker are 2 different benchmarks and I'm not sure how they compare. Besides that benchmarks rarely benchmark realistic code and the Nim blog doesn't mention being the fastest out there, but it mentions "native performance" which I feel like is a fair claim.
- dom96 5y agoYou definitely cannot compare a benchmark result you got on your machine vs. one in (what I believe is) a CI environment.