Welcome to the IBM TechXchange Community, a place to collaborate, share knowledge, & support one another in everyday challenges. Connect with your fellow members through forums, blogs, files, & face-to-face networking.
Join / sign up
As discussed in a past blog post , if you're experiencing performance problems, after you've reviewed that garbage collection (GC) is healthy , and you've reviewed thread dumps , the next step is to review a sampling profiler. This gives you more detailed information about what's using CPU...
2 Comments - no search term matches found in comments.
As discussed in a past blog post , if you're experiencing performance problems, after you've reviewed that garbage collection (GC) is healthy , the next step is to review thread dump stacks during a performance issue. This gives you a sample of what your application is doing and often leads to...
4 Comments - no search term matches found in comments.
As discussed in a past blog post , if you're experiencing performance problems, the first thing to check is whether your garbage collection (GC) is healthy. If the proportion of time in garbage collection is greater than ~10%, then garbage collection is likely unhealthy and the application is...
In our previous blog post , we discussed the value of running the Linux perf native CPU sampling profiler to investigate Java CPU usage in production. However, perf generally requires root access and OpenShift application containers generally don't run with such privileged access. This...
If your Java workload is experiencing high CPU in production, the basic workflow is generally the following. This article will quickly review the first three steps and then we'll focus on the fourth step in green: Review a native sampling profiler. Garbage Collection The first thing to...