4 ms·
I've used siege for a long time and never had any problems. However, I'm easily tempted by the new and shiny which led me to find another great HTTP benchmarki
by anonfunction 11y ago
I've used siege for a long time and never had any problems.
However, I'm easily tempted by the new and shiny which led me to find another great HTTP benchmarking tool: https://github.com/tsenart/vegeta https://github.com/tsenart/vegeta
- voltagex_ 11y agoHow do siege and vegeta compare to apachebench?
- anonfunction 11y agoSiege is very comparable but vegeta has a lot more output options such as graphs, JSON, CSV, etc... Another tool I forgot to mention was wrk (and now wrk2) which are unique in that they are scriptable via lua.
- tobz 11y agoAs a small follow-on, there is also Barrage [1], which is more of a framework than anything else. kellabyte wrote it to benchmark changes to Haywire [2], so it's geared towards configuring your client and server, and then collecting all of the metrics from both the client side, and the server side, and displaying them in an easy-to-digest format. This obviously isn't terribly useful if you're just trying to gauge request rates, or apply load, but it's very useful if you need a repeatable way to not only measure request rates but see how your server is doing under load. [1] https://github.com/kellabyte/barrage https://github.com/kellabyte/barrage [2] https://github.com/kellabyte/Haywire https://github.com/kellabyte/Haywire
- petard 11y agoonly used vegeta and ab and prefer vegeta. has many more options and stats, while still being easy to use as ab.