day95-performance stress test-optimization-heap memory tuning and simulation of online application memory crash and downtime

Previously, because dynamic and static separation was not configured, a dynamic request to visit the home page may carry dozens of static requests. Now, after dynamic and static separation is configured

Let's do the stress test again

Aggregate report

 Fill out the form

It can be seen that the throughput of obtaining the full amount of data on the homepage will increase after the separation of dynamics and statics, but not too much

 

As follows, I have been saying that because the new generation of memory is too small, frequent minor gc consumes a lot of time

Originally, our heap memory is set to: the maximum heap memory is 512m

Now set to the maximum and the minimum heap memory is 2048m, that is, the heap memory is 2048m, and the new generation is set to 1024m

Then, the stress test throughput has increased again

Fill out the form

Let’s simulate the downtime

Let me just say: I don’t need to simulate, set the heap memory to 100m, and then the heap memory is insufficient, and the application will be squeezed offline, and the home page cannot be accessed.

 

Guess you like

Origin blog.csdn.net/JavaCoder_juejue/article/details/113621639