Tag Info

New answers tagged


In regards to you screenshots in general and Summary Report in particular, as per The Load Reports guide the explanation of the report fields is: # Samples is the number of samples with the same label. Average is the average time of a set of results. Min is the shortest time for the samples with the same label Max is the longest time for the samples with ...


The options to precisely set desired throughput are in: Ultimate Thread Group (available via JMeter Plugins) provides easy visual way of defining virtual users ramp-up, ramp-down and time to hold the load. 3 users per hour will look like Constant Throughput Timer allows to set target load in "requests per minute" so if you want 3 requests per second ...


As far as I know jmeter doesn't work in a sequential order. What jmeter does is, it takes all the requests and send them to the server/host all at the same time. So if you have configured it for 3 users making 1 http(s) request, that is 3*1 http(s) requests will be sent to the server/host all simultaneously and then it will wait for the response!


Here you go, http://www.tutorialspoint.com/jmeter/jmeter_tutorial.pdf http://jmeter.apache.org/usermanual/index.html http://www.roseindia.net/jmeter/ http://jmetertutorials.blogspot.in/ http://www.jmeter.net/ Enjoy performance testing :)


java.rmi.server.hostname property can be set either in system.properties file (which lives under /bin folder of your JMeter installation) or passed directly to JMeter startup script via -D key as jmeter -Djava.rmi.server.hostname= This way you can specify interface to bind to. See Apache JMeter Properties Customization Guide for more details ...


First you need to define what the "breaking point" is. There are a number of possibilities. The obvious problem would be if the web server itself crashes and stops responding, but there are a number of problems that can occur well before that point that in most cases would still be considered "broken". Some other problems that could tell you your ...


To determine the breaking point of you application increase the thread count gradually with each test run. At present you have it as 10. Now try testing with 20, then 50 in third iteration. Now suppose you find out that you application broke at 50 threads, then reduce the thread count to 40 and run the test again. Let's say your application works fine with ...

Top 50 recent answers are included