Use performance testing to troubleshoot high memory usage on the service line

Problem scenario: 1 machine is produced, and the memory usage of the report service process is high, which affects the availability of the next reminder function.
Reason: the poi object used by the component that exports the excel file in real time is not destroyed in the jvm permanent generation memory, resulting in the permanent generation memory failure Recovery
Solution: call the cose method of the workbook in time to release the reference relationship of the related poi export related objects.
Troubleshooting tool: jmeter/jmap Rescue
scene: first, construct 100,000 data. Simulate the production mixed transaction business operation in the pressure test environment of the electric task details, and log in to the electric task details page to initiate the export of 100 electronic task details reports. At this point, observe the trend of server cup occupancy and memory occupancy through jmeter.
Stress test data analysis ideas: 1. At key time points, before stress test, start stress test, before launching export request, export request processing, after export request processing, observe the inflection point of jmeter performance, and use jmap to view the heap memory value as an auxiliary reference .

Guess you like

Origin blog.csdn.net/feifeixiongxiong/article/details/110425569