Jmeter5.x Pressure test interface actual combat – QPS comparison before and after interface performance optimizationClick on the subtitle to watch the video

Introduction: JMEter5. x pressure test interface practice – QPS comparison before and after interface performance optimization

  • Hot data interface pressure test

    • QPS: (Query Per Second): the number of requests Per Second, which is how many requests are processed by the server in one Second

     

  • New Aggregate Report: Thread Groups -> Add -> Listeners -> Aggregate Report

Lable: Sampler's name Samples: How many requests will be sent, for example, 10 users, through the loop 10 times, 100 Average response time, Median response time, 90% Line: 90% of the users' responses will not exceed 95% of the time (90% of the samples took no more than this time. The remaining samples at least as long as this) Line: the response time of 95% users does not exceed 99% Line: the response time of 99% users does not exceed 99% min: the minimum response time Max: Throughput -- By default, it expresses the number of requests completed per Second. QPS, TPS KB/Sec: the amount of data received per SecondCopy the code

  • Pressure measurement based on current machine configuration

    • No cache interface is used
    • Use the cache interface

  • Problems with the current architecture

    • The distributed cache and the application server network require Intranet communication

    • You can deploy Redis locally for testing

Little Drop Classroom -Redis6 Study Notes