Simulating & troubleshooting CPU spike in Kotlin

This article describes how to simulate a CPU spike in Kotlin using an example program that launches six threads running infinite loops. It explains methods for troubleshooting high CPU consumption through both manual and automated approaches, highlighting the use of the yCrash tool to identify problematic threads and code lines causing the issue.

Troubleshooting App unresponsiveness due to Oracle DB

The application experienced a slowdown when connecting to Oracle RAC due to resource constraints, impacting response times. Troubleshooting involved using the yCrash script for artifact collection and analysis, revealing that 46% of threads were blocking on database calls. The Oracle DBA confirmed resource issues, which, once resolved, restored normal application performance.

Troubleshooting deadlock in an Apache opensource library

Apache PDFBox is a Java library for handling PDF documents. A recent deadlock issue was identified, blocking two threads that were waiting for each other's resources. Troubleshooting involved capturing thread dumps and analyzing them, which led to filing a bug report with the Apache PDFBox team, who promptly addressed the issue.

Up ↑