Two scene design jmeter performance testing (b)

A, stepped scenes

  The scene is mainly used in the test load inside, by setting a certain number of concurrent threads, given the pressure rule, follow the "slow start, the end" principle, continue to increase concurrent users to find performance bottlenecks in the system, then there is for all aspects of system optimization

  Use the thread is: jp @ gc - Stepping Thread Group (deprecated)

  

 

  While adding listeners are:

  • TPS:jp@gc - Transactions per Second
  • Response time: jp @ gc - Response Times Over Time
  • Number of active threads: jp @ gc - Active Threads Over Time
  • Hits: jp @ gc - Hits per Second

    

  Stepped for the parameters of the scene, as follows:

  • This group will start: the number of concurrent users of the given current load
  • First, wait for: Wait XX seconds started
  • Then start: 0 seconds (initialization) concurrent users start XX
  • Next, add: start XX number of users within each using ramp-up time
  • threads every: each pressing step the user has completed holding operation after startup XX seconds
  • Next start number of users within XX seconds to complete, add a: using ramp-up
  • Then hold load for: This group will start all concurrent users remain running start after the completion of XX seconds
  • Finally, stop: every threads every time the number of users to reduce XX
  • threads every: reduce the number of users every XX seconds Finally, stop the

   

 

   Description: Given the number of concurrent users to the load 100, 0 seconds from the start, to increase the number of simultaneous users 10 every 2 seconds, 2 seconds after the start time of the completion of 10 concurrent users begin to run smoothly for 20 seconds, turn it until 100 after all concurrent users start completion, the smooth run for 60 seconds, and then reduced every 1 second until five concurrent users to reduce the number of concurrent users is 0, the load test is finished.

  After completing the listener can go to view a variety of monitoring results

Second, the wave-scene ( Universal scene design )

  The scene is mainly used in split time pressure measurement and stress testing inside, split time pressure measurement systems such as cash registers, will one day appear peak, plateau and leisure area, for this scenario we have to be designed to pressure values ​​for different time periods different ways in different pressure, etc., stress tests we only need to use a scene, and the pressure measurement time can be set long, the same report also obtained with test monitors jpgc

  Use the thread is: jp @ gc - UItimate Thread Group

  On the test plan: right click -> Add -> thread (user) -> jp @ gc - UItimate Thread Group

   

  Wave parameters for a scene, as follows:

  • Start Threads Count: given the number of concurrent users of the current time period
  • Initial Delay, sec: initialization time, unit: seconds (s)
  • Startup Time, sec: start time, unit: seconds (s)
  • Hold Load For, sec: all concurrent users start a long hold operation is completed, unit: seconds (s)
  • Shutdown Time: end time, unit: seconds (s)

  Let's use this design a ladder of test scenarios it, as shown below

   

  This means that the number of users increasing trend is 10 - 50 --- 100--200--500

  10 starts the user does not start delay 2s, 600s running, pressurized to 50 users, 50s delay start, start length 5s, 550S continuous operation, the user then pressurized to 100, 100s delay, activation cost 5s, 500s continuous operation, continue pressurized to 200 users, the delay 150s, start consuming 5s, running 450s, and finally pressurized to 500 users, the delay 200s, start consuming 10s, continued to run the 400s, the final stage of consumption by the user 2 seconds to stop

  We redesign measured segment time pressure wave or pressure detected scene scene

  

 

   Item Start 50 users without delay, the start 10s, pressure measuring 300S, 20s after 30 new user, starting five seconds, start to finish under reduced pressure, then the user 150s plus 40, completion of decompression start 10s, running after the 100s, 50 new user, start in the 10s, 20s continued operation pressure, waiting for the first start of the last 50 completed the user can stop the pressure

 

  

   

Guess you like

Origin www.cnblogs.com/hally/p/12662134.html