4 ms·
How is this "insanely fast"? Running an example main with the route '/' mapped to return "Hello World" ab -n 10000 http://127.0.0.1:8080/ I get 1400 requ
by mpweiher 11y ago
How is this "insanely fast"?
Running an example main with the route '/' mapped to return "Hello World"
ab -n 10000 http://127.0.0.1:8080/
I get 1400 requests/s in debug mode and 1900 requests/s in release mode.
With wrk, I actually get between 3000-4000 requests/s with default parameters. Most of the time. Sometimes it just hangs. Trying to increase the number of requests with the -r parameter made the hangs consistent, I was not able to get wrk to finish in more than a dozen attempts, so there appears to be a problem with it dying under load.
For comparison, the built-in Apache gets 15000-20000 requests/s, my own web-framework based on libmicrohttpd + an Objective-C/Objective-Smalltalk wrapper gets around 25000-32000. None of these would be classified as "insanely" fast, and they are around an order of magnitude faster than this. It's actually a lot closer to Ruby/Sinatra (~600 requests/s).
EDIT: project readme says "insanely", not "blazingly", so updated.
- geocar 11y agoIt is perhaps not the definition of "insane" that you are looking for.
- boomlinde 11y agoIf so, one that ignores the performance of the alternatives.
- endymi0n 11y agoAt least the insanely fast speed of Vapor also goes well on the client side with Vapor.JS, the world's smallest and fastest JavaScript library: https://github.com/madrobby/vapor.js/tree/master https://github.com/madrobby/vapor.js/tree/master
- TazeTSchnitzel 11y agoI prefer VanillaJS: http://vanilla-js.com/ http://vanilla-js.com/
- tannernelson 11y ago"insanely" fast was meant as a comparison to languages like PHP and means both performance and time it takes to set up.