Only at the end of the startup period we can see a spike in the garbage collector graph and a dramatic decrease in used memory. But if we look at the GC Activity graph during the startup period the memory increases, we observe that the garbage collector did not run (activity at 0%). Depending on the options we select, when starting the profiling session, it shows us the memory, garbage collector activity, recorded throughput, CPU load and many more.įor example, this is the memory graph for the startup of a service.įor someone who has never dealt with a memory leak, looking at this graph, he might think that a memory leak occurred as the memory usage is increasing continuously. JProfiler displays several graphs after it has started up. We will take a look at a memory leak and investigate how it would be possible to detect using the tools that JProfiler offers. ![]() ![]() There are many blog posts and articles about different kind of memory leaks and how their memory footprint looks like, unfortunately, it is very hard to find the memory leak based only on the memory graph. JProfiler brings many more features, like database profiling but these are out of the scope of this blog post. It provides many useful tools such as memory profiling, a way to analyze heap snapshots and a live memory view that shows all objects that are currently in use. ![]() JProfiler is a java profiler developed by ej-technologies that helps developers resolve performance bottlenecks, find memory leaks and understand threading issues.
0 Comments
Leave a Reply. |