Comparison of several Java performance analysis tools

During maintenance of the customer's application, I noticed some performance problems under high load. Theoretically, increasing the load on the application will reduce the performance and other ratios. However, I think the performance drop rate is much higher than the load increase. I also found that performance can be improved or even reached by changing the logic of the application. To learn more about this, we need to perform some performance analysis. Naturally, we need to use some analysis tools. | Spring InsightSpring's actions and efficiency are indeed very high. At last week's Google IO conference, it was just announced that a new version of Spring Insight will be launched and Google Speed Tracer will be seamlessly integrated. It will be released this week. It is strongly recommended that developers learn and use this development tool to improve the quality and performance of your applications. | JProbeIn the wide application of Java, although the advantage has been promoting the unprecedented development of J2EE, there are often some troubles, that is, people are often disappointed with the performance of J2EE applications. Therefore, we need some tools and investigation strategies to help the J2EE development team solve these performance problems. This is the problem to be solved by Quest JProbe Profiler and Jprobe Memory Debugger. | YourKitYourKit Java Profiler is an industry-leading Java profiling tool. The Analysis of CPU and memory has always been very difficult. YourKit has created a revolutionary analysis tool. The application in the development and production stages has brought tremendous benefits to professional Java developers. This article introduces the performance analysis software yourkit. | JProfilerJProfiler is a Java performance monitoring tool. You can view the object, object reference, memory, CPU usage, thread, thread running status (blocking, waiting, etc.) of the current application, and find the hotspot used by the application memory, there are several articles for reference: Getting, introducing, getting started, and using JProfiler to solve practical problems. These articles have basically introduced common things. Here we will talk about snacks. | VisualVMWhen a Java multi-threaded program is running, we do not know what happened in most cases. Only when an error log is generated can we know that there is a deadlock in the original code. Aside from the code check tool, we will first discuss how to use visual VM monitoring to analyze the running status of multiple threads.