IIRC, ab (ApacheBench) is still vulnerable to Coordinated Omission which makes its 95%ile latency measurements useless. wrk2 solves that
JMeter has a lot more features like following links instead of just pulling the same URLs over and over, but it’s also very resource intensive. On a typical dev machine (32G 5800x3d) it is very slow and crashes when running at an absurdly low rate like 1000 requests/second. So unless your website is hosted on a Raspberry Pi, you’d have to spin up 100 cloud VMs to do a real load test. At that point running full browsers with Selenium starts to sound reasonable.
Comments
Tried, tested and true solutions: JMeter and ab, both by Apache
IIRC, ab (ApacheBench) is still vulnerable to Coordinated Omission which makes its 95%ile latency measurements useless. wrk2 solves that
JMeter has a lot more features like following links instead of just pulling the same URLs over and over, but it’s also very resource intensive. On a typical dev machine (32G 5800x3d) it is very slow and crashes when running at an absurdly low rate like 1000 requests/second. So unless your website is hosted on a Raspberry Pi, you’d have to spin up 100 cloud VMs to do a real load test. At that point running full browsers with Selenium starts to sound reasonable.