Hi, > I am attaching our website statistics for 5 min blocks. Based on this > statistics, please help me to develop a performance test plan. The goal of > my test is to make sure that no page loads in more than 10 seconds.
Haven't looked at those, but want to answer generally instead. > 1. How many concurrent users (threads) should I create? As many as necessary. Watch the average and max page load times (using e.g. the Summary Report Listener). > 2. What ramp-up I should set? I have often ramped up at 10 threads per second up to a chosen max number, then let that constant number run for a duration. Rinse and repeat, with a new (higher) max. You might just as well want to ramp very slowly (10 threads per minute or somesuch) and watch the increasing server load. In this scenario, it is a good idea to clear your Listeners each couple of minutes, as you probably don't want to accumulate the sort of data they are gathering. > 3. How many loops? Depends. My test plans usually involve one loop per "activity", meaning there are different things a visitor can do (shopping for stuff, browsing reviews etc.) and each thread picks one of those tasks at random. Using a loop, it repeats its set of activities a somewhat random number of times. You can well build test plans without using any Loop Controllers, though. Just have your Thread Group do the looping, or even loop indefinitely and limit the test time using the Scheduler. HTH, Felix --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
