Tag: Java

7 habits of highly effective Performance Troubleshooters! – All Day Devops Conference

The World’s Largest 6th Annual All Day DevOps conference held on October 28th 2021. Our architect Ram Lakshmanan was invited there to present a webinar on the topic 7 habits of highly effective Performance Troubleshooters!

Below is the deck shared in the conference which explains, how to forecast the problems?, what to do when the problem is happening?, how to identify the root cause instantly? and how to prevent problems from happening in the future and so on.

Continue reading “7 habits of highly effective Performance Troubleshooters! – All Day Devops Conference” →
0

Performance impact of java.lang.System.getProperty()

‘java.lang.System.getProperty()’ is a common API used by Java developers to read the System properties that are configured during application startup time. i.e. when you pass “-DappName=buggyApp” as your application’s startup JVM argument, the value of the ‘appName’ system property can be read by invoking the ‘java.lang.System.getProperty()’. Example:

Continue reading “Performance impact of java.lang.System.getProperty()” →
7

Overhead added by Garbage Collection Logging

Enabling Garbage collection logs on your application has certain advantages. In nutshell, Garbage collection logs will facilitate you to optimize Garbage Collection pause time, improve overall application’s response time, forecast production outages, reduce computing cost. Even though Garbage collection logs have these advantages, we weren’t sure what overhead does garbage collection logging add to the application. Thus we set out to conduct the below case study.

Continue reading “Overhead added by Garbage Collection Logging” →
6

Overhead added by collecting thread dumps

A thread dump is a snapshot of all the threads running in a java process. It’s a vital artifact to troubleshoot various production problems such as CPU spikes, unresponsiveness in the application, poor response time, hung threads, high memory consumption. Thus to facilitate troubleshooting, we have seen enterprises capture thread dumps on a periodic basis (every 5 minute or 2 minute).So we were curious to learn the overhead of capturing thread dump on a periodic basis. Thus we set out to conduct the below case study.

Continue reading “Overhead added by collecting thread dumps” →
2

Powered by WordPress.com.

Up ↑

en English
ar Arabiczh-CN Chinese (Simplified)nl Dutchen Englishfr Frenchde Germanhi Hindiit Italianpt Portugueseru Russianes Spanishta Tamil