Jmeter concurrent user load Test Plan

Question

I am new to Jmeter. My project Manager said to me to test the website load with 100 concurrent user.

Following functionality of website considering to load test-

1. User Registration

   • Get Registration Page Request
   • Post Registration Page Request

2. Login and User profile navigation

   • Get Login Page request
   • Post Login page request
   • Get User Dashboard request
   • Get edit Profile page request
   • Get change password request
   • Get Invite Friend Page request

My Test Scenario is 50 concurrent user Accessing Registration page and other 50 concurrent user accessing User profile(login,dashboard, etc) . I have created following test plan for the same -

And did thread configurations for registration and Login same as -

Total No of Threads : 50

Rampup period : 600 sec

Duration of holding load : 3600 sec

Configured constant timer (delay for each request 200 ms) for both Thread Group requests also added some listeners for collecting the result. I have following question -

1. Is it correct way to include these many request in test plan for complete load test of My website ?

2. Do I have configured right thread properties or what else I can do for achieve the best ?

Answer 1

1. Think Time

   Your test plan looks good, however the current configuration doesn't represent 100 concurrent users as 200ms think time is something for "superhuman". Real users "think" for a longer period between operations and it should vary depending on the nature of simulated request. So I would suggest using individual Uniform Random Timers with the relevant think time ranges for each request.

2. Overall Test Design from the "reality" perspective

   If you have some extra time you could think about bringing more reality into your simulation like:

   • X users perform registration
   • Y users editing their profiles
   • Z users inviting friends
   • etc.

   So distribution would represent normal anticipated usage of your application. Your load test should be as realistic as possible, only this way you will be able to tell for sure "my application is able to support this many users providing reasonable response time". Take a look at Throughput Controller

3. Overall Performance

   • Disable Active Threads Over Time and especially View Results in Table listeners during test run
   • Configure PerfMon Metrics Collector listener to store the captured values into a file. Later you will be able to open the file and analyze the metrics
   • Run the test in non-GUI mode
   • follow other recommendations from 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure