I am testing my API with below gatling3 code
setUp(scn.inject(constantUsersPerSec(300) during (10 minutes))).throttle(
reachRps(300) in (10 seconds),
holdFor(5 minutes),
reachRps(500) in (10 seconds),
holdFor(5 minutes)
).protocols(httpProtocol)
what I am expecting is in first 5 minutes, gatling sends 300 requests per seconds and in the next 5 minutes, gatling sends 500 requests per seconds. However the test report shows that gatling sends 300 requests per seconds in all the 10 minutes.
why does this happen?
What you'll want to do is something similar to this:
setUp(scn.inject(constantUsersPerSec(500) during (10 minutes))).throttle(
reachRps(300) in (10 seconds),
holdFor(5 minutes),
reachRps(500) in (10 seconds),
holdFor(5 minutes)
).protocols(httpProtocol)
The throttle will be the upper limit your test, so if you have a constant users per second of 500, but throttle it for 300, it will stay throttled to 300, but then once you increase the throttle to 500, you should see the rps rise to that threshold, given constantUsersPerSec(500) gives you enough traffic to get you to that point.
I think the period showed in your graph is the initial period of the test, where to 12:21 from ~12:31 is reached 300 rps. after that, the gatling will hold for 5 minutes and then make 500 rps by more 10 seconds. You waited 10s + 5 min + 10s + 5min?
Related
I am trying to send 1100 requests per minute to my API endpoint for a period of 5 minutes, so in total, I will make 5500 requests to the endpoint.
Based on the above requirement, Here is how I have set up my Jmeter:
It seems like I have misconfigured Jmeter, because in the end I can see Jmeter has made 8401 requests to the API instead of 5500.
What have I missed in the configuration?
Does the "Infinite" check-box need to be checked or unchecked?
The number of requests you're expecting (which is 5500) for this test plan is wrong.
As per your expectation, I think, you are making confusion between the Threads and Requests.
Ramp up is the time in which all the users arrive on your tested application server.
Requests are simulated by samplers but threads are the simulation of users.
According to your test plan:
- Total Number of Threads: 1100 vitual users
- Ramp-up time: 60 (1 min)
- Loop count: Infinite
- Test duration: 300 sec (5 min)
- No of requests/sampler in Test Plan: Unknown, assuming it 1
JMeter Execution:
JMeter will kick off those 1100 virtual users in 60 seconds according to the ramp-up time. So, (1100/60)~ 18 users will be active in every second for the first minute of your test. Each thread/user will execute the requests or samplers you have defined in your test plan hierarchy. As you have defined the loop count to infinite, each thread will execute the requests repeatedly until the test finishes. After 60 seconds, all of your 1100 users will be actively hitting those samplers/requests for the remaining 4 mins.
So the total number of requests you will be able to make through JMeter depends on your application response time.
If the avg response time of your requests is 1 second (assuming you have only 1 requests in your test plan), then you will be able to hit total 264000 (264000/240 = 1100 requests per second) for the last 4 mins (when all of your 1100 users are active) of your tests. You can also verify this accordingly by using Active Threads Over Time and Hits Per Second listeners.
So, Please double check the avg response time of your application or the requests/samplers you are using in your test plan.
If you want to control JMeter's throughput to 1100 per minute, you can use a Constant Throughput Timer at your test plan level and use target throughput value as 1100.
Do not forget to add the count of ramp-down time in your test duration. Yes, when you ramp up i.e. in the first minute generally you get more requests as threads are starting. In your case, your test duration should be 7 mins (60 seconds for the ramp-up 1100 users + 300 seconds for 5500 requests + 60 seconds for the ramp down for 1100 users).
You can also check this thread for more : How should I calculate Ramp-up time in Jmeter.
Please note- The total number of requests is related to throughput, Whereas the number of active threads performing the same activity is related to concurrency.
I am trying to send 1100 requests per minutes to my API endpoint for a period of 5 minutes, so in total I will make 5500 requests to the endpoint.
I don't know how you came with this 5500 number but this is not very correct.
Your setup means that:
JMeter will add 18 virtual users each second for 60 seconds
After 60 seconds pass JMeter will run 1100 users for another 4 minutes
The total number of requests JMeter will be able to make will mostly depend on application response time.
If you want to limit JMeter's throughput to 1100 requests per minute consider using Constant Throughput Timer or Precise Throughput Timer
If you don't want to limit JMeter's throughput but want 5500 executions either:
Set "Loop Count" to 5 (but in that case you might fail to get 1100 concurrent users)
Or use Throughput Controller in Total Executions mode so JMeter would stop after executing 5500 requests
I want to get fluctuation in TPS using JMeter like given below
1 TPS to 10 TPS -- 60 minutes
2 TPS to 4 TPS -- next 60 minutes
10 TPS to 15 TPS -- for next 60 Minutes
1 TPS to 3 TPS -- for next 60 minutes
How to achieve such various TPS with respect to time.
I am using jmeter 4.0
My Requests are like
Login Application
Create Order
Active Order
Disconnect order
Cancel Order
Users: 300
Ramp Up: 300 seconds
Duration 4 Hours (14400 seconds)
Application can handle upto 45 TPS (Already Tested this)
Here we want to Check Semaphore and Server Res. memory are increasing/decreasing as per TPS increase/Decrease. (This is my target of this test)
For Your case you can use below link to understand the tree to create and use of throughput controller-
Purpose of Throughput Controller?
And I would suggest you to use multiple Once only controller and apply throughput controller with each of them and define the throughput values you want to achieve one by one, For Example
Thread Group
Runtime Controller (60 minutes)
once only controller
HTTP Sampler
Throughput controller (1 TPS to 10 TPS)
Run-time Controller (next 60 minutes)
Once Only Controller
HTTP Sampler
Throughput Controller (2 TPS to 4 TPS)
You can see the progress in listeners( In graphical form).
Hope It works :)
You should work with Ultimate Thread Group
In your case 3 lines with Hold Load For 3600 seconds
Each line will have different Initial delay, first is 0, second is 3600 (hour) and third is 7200 (2 hours)
My performance test strategy is to use JMeter to send 3 different requests to a linux server continually. They are Init, Calculate and Apply.
The number of active users of peak hour is 40 and the number of each request per hour is 200. The load test should be conducted with the peak usage with no less than one hour.
If my understanding is correct, running the test for two hours eventually there will be 1200 samples shown in the result table (200 requests * 3 * 2 hours). However, with the following configuration there are much more samples sent to the server.
Thread Group:
- Number of threads: 200
- Ramp-up time: 3600 seconds
- Duration: 7200 seconds
I have also tried setting the number of threads 50, the result is still far more than my expectation.
May I know how to configure the JMeter correctly ?
Your configuration should be:
Number of threads : 40
Ramp-up time: Should be short in your case, its value tells in how much time threads will go from 0 to 40.
Duration is ok
Finally, as you want 200 requests per hour, which would be 600 for the 3 ones, it would be 10 per minute, you need to use Constant Throughput Timer inside a Test Action:
Where Test Action is :
I have about 300 users (configured in the thread group) who would perform an activity (e.g.: run an e-learning course) twice. That would mean I need to expect about 600 iterations i.e 300 users performing an activity twice.
My thread group contains the following transaction controllers:
Login
Dashboard
Launch Course
Complete Course
Logout
As I need 600 iterations per 5400 seconds i.e 3600 + 900 + 900 seconds (1 hour steady state + 15 mins ramp-up and 15 mins ramp-down), and the sum of sampler requests within the total thread group are 18, would I be correct to say I need about 2 RPS?
Total number of iterations * number of requests per iteration = Total number of requests
600 * 18 = 10800
Total number of requests / Total test duration in seconds = Requests per second
10800 / 5400 = 2
Are my calculations correct?
In addition, what is the best approach to achieve the expected throughput?
Your calculation looks more or less correct. If you need to limit your test throughput to 2 RPS you can do it using Constant Throughput Timer or Throughput Shaping Timer.
However 2 RPS is nothing more than statistical noise, my expectation is that you need much higher load to really test your application performance, i.e.
Simulate the anticipated number of users for a short period. Don't care about iterations, just let your test to run i.e. for an hour with the number of users you expect. This is called load testing
Do the same but for longer period of time (i.e. overnight or weekend). This is called soak testing.
Gradually increase the number of users until you will see errors or response time will start exceeding acceptable thresholds. This is called stress testing.
Please help me to achieve this type of load testing in Jmeter,i have configured Scheduler configuration but it is not running as per Duration as 60 minutes with in 10 seconds it is completing the requests and my Vusers -5 and Loop Count-50
Please help how to prepare this type of scenarios.
If you need 200 requests - decrease loops count to 40 (5 users x 40 loops == 200 total requests)
Also consider using Constant Throughput Timer or Throughput Shaping Timer to limit the throughput to 200 requests per minute (something like 3.3 requests per second).