JMeter Stress testing
Posted
by mcondiff
on Server Fault
See other posts from Server Fault
or by mcondiff
Published on 2010-04-01T21:27:20Z
Indexed on
2010/04/01
21:33 UTC
Read the original article
Hit count: 646
jmeter
|stress-testing
MAMP server hosting a Joomla instance.
I'd like to hear the community's thoughts on the best way to stress test the server and find it's breaking point on concurrent users etc. Currently I have setup a test plan which I have going to the home page, grabbing the index.php, css, js and all images and have run tests on 1 to 100 users and a varying number of loops.
What I'd like to know is how do I determine at what number of concurrent requests or looping requests is a good way to gauge if my server can handle the proposed increase in traffic?
What is a good KB/sec, Throughput, Average, Max, Min via the Aggregate Report and at what number of threads/loops etc?
I have googled and have not found immediate answers to these questions and thought to come here.
More or less I have just used this http://jakarta.apache.org/jmeter/usermanual/jmeter_proxy_step_by_step.pdf to guide me and then I have been winging it in terms of Thread and Loop numbers.
Any light shed on these subject would be much appreciated.
© Server Fault or respective owner