Sunday, June 16, 2013

Load Testing - Jmeter Vs Siege

- Jmeter comes with a GUI to create/run load tests, while Siege is command line tool
- Jmeter has tons for features that can be used while testing an entire website - with muliple pages, while Siege has limited options to be used
- Siege is fast to setup and run while Jmeter takes time to setup as it involves multiple steps
- Jmeter is faster to run for n concurrent users than Seige
- Jmeter has broad set of options for results analysis while Siege has one summary of results
- Seige is good for a quick load testing of a webpage while Jmeter is good for a wide variety of tests to be run at a single time
- Jmeter has several plugins to enhance its load testing features and analysis while Siege lacks in plugins
- Sometimes, Siege can give false results thinking better performance while Jmeter is quite accurate in its results

Hence, I prefer Jmeter in most of the load testing requirements, while I use Siege for a quick load test.

1 comment:

Dan said...

Do you have data to support the performance-based claims on jMeter? I have no argument with flexibility. When measuring something slow, like the response time of my search server (because there is I/O, and it is an application, JMeter is waay better).

When measuring something very fast, like plain-old-files on Apache event mpm vs Nginx, maybe JMeter is not so good.

The temptation is to run JMeter on my windows desktop, rather than develop the jmx file there and then run it on the server.