Jmeter Ramp-up second is dependent on number of request(Sample) and time between sampler inside Thread



  • For example, there is a thread group named login.

    Now this login thread group has 10 request where all requests are parameterized(One API request dependent on other) and time b/w request is 1 secs(Used constant timer)

    My question is what is the required ramp up second for thread group?

    According to actual calculation read from various sources.If i give thread count 50 and ramp-up seconds as 50 then the time b/w thread is 1 seconds where 50 users will be created in 50 seconds but if i use this scenario how the time b/w request inside the thread will be handled.To run 10 request at least jmeter need 10 seconds since i have used timer

    If my scenario is correct then the actual rampup seconds will be dependent on number of request and time b/w request.

    Then the Ramp-up-seconds should by calculated as below

    Ramp-up-seconds=product of(No of requests,time b/w requests inside thread,No of thread count)

    Please make some review on my scenario and provide a answer. If i work with actual Ramp-up-second calculation API paramaratization doesn't works properly and my jmeter load test script gets failed

    Jmeter Test script will be like as below

    1. Make login: Will perform login and extract the authorization token for further requests
    2. create User: Will created user and createduserid will be extracted from response
    3. Fetch User Detail: Will fetch the userdetail for created userid
    4. Logout: Will perform logout

    So this should be happen in sequence

    and the time b/w request inside thread is 1 seconds used constant timer



    1. Each JMeter thread (virtual user) is executing Samplers upside down, in your case sequentially.
    2. Ramp-up doesn't have any impact either on other threads or on sequence of requests execution

    The main idea of the ramp-up (and eventually ramp-down) is that it's better to increase the load gradually, this way you will be able to correlate increasing load with other performance metrics (throughput, response time, number of errors, etc)

    If your script fails the reasons could be in:

    1. Your correlation logic fails somewhere somehow, inspect variables you're passing between requests using Debug Sampler and View Results Tree listener combination
    2. Your application gets overloaded hence fails to provide normal responses, check response body for failed requests and for Samplers immediately previous to failed requests, application logs, whether the application has enough headroom in terms of CPU, RAM, etc. using JMeter PerfMon Plugin

Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2