It will probably help if you go through some literature on performance testing . There should be some free books online. All numbers below are just examples , use the values for your system
>1. How many concurrent users (threads) should I create? There are two things to note here. You normally wont test with just a single number of current users but you will probably vary this number. (10 users making 100 requests each != 100 users making 10 requests each , even though both give you 1000 requests at the server). The maximum number is dictated by your application's SLA (e.g. your business says at peak times I want atleast 100 users to be able to access x,y,z functionality and the response time should still be less than for e.g 5 seconds). The minimum number you might choose to start with is an approximate calculation. From your screenshot say you need 1500 requests in 5 minutes and lets assume on average your page is returned within 2 seconds. So a single user would in 5 minutes be able to make (5*60)/2 = 150 requests (Assuming zero think time). Therefore if you wished to have 1500 requests per 5 minutes you need atleast 1500/150 = 10 threads. Any load below this wont be able to generate 1500 requests. So you need to have a minimum of 10 threads - But you'd probably choose a value higher than this to start with - If you wanted to simulate real life behavior , you'd have to add a pause between requests , but this will cause the number of requests to decrease which means to generate the same load you'd have to increase the number of threads. Also you might want to keep the load at the level you are seeing. In which case you'd increase the threads but put in a constant throughput timer so that you still see the same load. >2. What ramp-up I should set? Any number is fine , its usually used to protect the server from seeing a burst that it might not be able to handle. lets say the calculations above resulted in you having to test with 50 threads, but because of timers / delays etc it may turn out that any point of time the server only sees 20 concurrent sockets. If you have no rampup then the server sees 50 connections immediately which might cause your tests to get errors/ lower values than it should >3. How many loops? There are a lot of transient variables (network bandwidth, application caches, one time static loading of classes , lazy loads by DB etc) due to which you shouldn't rely on a single loop. Any number that gives you confidence that the values you are getting are accurate (the numbers shouldnt wildly vary for the loops). Typically I have a run to eliminate some of these variables (my application uses a cache so first time hits result in slower db calls but next time the cache should be hit) and then run the actual tests. On Thu, Sep 9, 2010 at 1:09 PM, Prostak <[email protected]> wrote: > > > Depends on the server, but many have a stats module that shows the > > current load - or you can analyse the server access log. > > I see everything comes down to these stats. I thought that the statistics > in > the first post would be enough... What exactly do I need to ask my server > guys? If I ask for server stats data, will they understand what I need? Can > you help me to phrase this question? I want to be very specific in my > request. As soon as I get this data, I will share it here to determine the > load plan. Thanks. > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Test-plan-for-970-page-requests-every-5-min-tp2826174p2834078.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
