Detecting CPU spikes in a Java application is important for keeping it running smoothly. This can happen because of things like lots of calculations, user actions, other tasks running in the background, or code that could be made better. The post talks about fixing CPU spike issues in Dell Boomi servers and doing tests to make CPU spikes happen in Boomi using the buggyApp tool. It also mentions using performance monitoring tools for keeping an eye on performance and figuring out why problems happen.
Chaos Engineering – Storage Saturation
Production environments frequently face space shortages due to growing disk usage by files like logs, databases, and output files. Failing to monitor and manage these files can lead to application crashes. The article explores simulating disk storage issues, offering a sample program, and strategies for diagnosing storage saturation, including manual and automated approaches using monitoring tools.
Troubleshooting CPU Spike on ServiceNow MID Server
This blog post addresses troubleshooting JVM CPU spike errors on ServiceNow servers, focusing on simulating such spikes using a Java program on the MID Server. It outlines causes of CPU spikes and guides on setting up the MID Server. yCrash is introduced as a monitoring tool that effectively diagnoses CPU spike issues and aids in resolution strategies.
Simulating & troubleshooting deadlock in Kotlin
This post discusses deadlocks in multi-threaded applications, particularly in Kotlin. It defines deadlock, illustrates it with an example involving trains, and provides a sample Kotlin program demonstrating deadlock between two threads. The post also suggests troubleshooting methods, including using thread dumps and the yCrash tool for root cause analysis.
