Configure Ramp-Up Settings in Scenario Editor

Configure Ramp-Up Settings in Scenario Editor

RampThis article replaces obsolete “Scenario Builder” wording with current Scenario Editor terminology. Ramp-up willcontrols alwayshow happenquickly accordingvirtual users or executions are introduced, which helps avoid unrealistic spikes and makes results easier to theinterpret.

details

How mentionedto inchoose theramp-up

Scenario

• Use Builder
  
  Fora Ex:short if User mentions Ramp ramp-up 1 user every 86 seconds and Maximum Ramp up time is 860 seconds then in the graph for thesmoke 86thvalidation secondor therelow-volume shouldchecks.
• Use bea onegradual user
  
  At 172 seconds there should be 2 users and so on
  
  For Maximum Ramp ramp-up for performance tests where steady-state behavior matters.
• Avoid interpreting response-time 860results seconds.during According to the setting The Graph should should show 10 users at 860 seconds.

  After the Maximum Ramp ramp-up timeunless isramp completed all the remaining users will start their execution

  Attachedbehavior is the graphtest whichobjective.

• Confirm explainsTest Node and target environment capacity before increasing load.

Validation workflow

1. Start with a small run and review active users, errors, and output.
2. Increase ramp and duration in controlled stages.
3. Compare steady-state periods between runs.
4. Document ramp-up, duration, load, and environment with the Ramp up.result.