On 2 December 2011 17:26, Tanakiat Srisaranayakul <[email protected]> wrote: > Please see my answer inline. > > In my case, the nb of users is almost the same all day, does that mean I >> have to put "1" for the ramp-up period ? >> > If the machine running jmeter is not good enough, 500 thread cannot be > started in 1 second. Are you ok if it's not 500 concurrent thread at 1st > sec?
Even with a longer ramp-up, 500 threads may be too much for one JMeter or even a single host; might need 2 or 3. You can check the absolute limit for JMeter by replacing your samples with a Java sampler, or perhaps an HTTP sampler reading a file. If you have a fast local server, you could also test against that, which will help show any limitations on network resource usage. Use a similar amount of data per request if possible. However, by reducing the timeouts, one can reduce the number of threads but still maintain the same load on the server. [JMeter can generate requests much faster than a human] The important measure here is the request rate as seen by the server under test. Whether it is generated by lots of single users or fewer faster threads probably won't affect the server response time as much as the total load. You can certainly get useful information from such a test. If you want to test with more users, you will most likely need to use multiple JMeters and hosts. > Also how can I simulate a test day during 8 hours? Is the scheduler (with >> start time and end time) useful for that ? >> > If you'd like to test for 8 hour and 1 time, it's ok to use jmeter > scheduler. If you'd like to run some kind of longevity test for few days, > you may need to consider OS scheduler to execute the script daily. > > How do I set my script to set up 10 operations per user per hour ? >> > Throughput Controller should fit your requirement > http://jmeter.apache.org/usermanual/component_reference.html#Throughput_Controller --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
