When the application's memory is under-allocated, it will result in the following side-effects: a. Transactions response time will degrade b. CPU consumption will spike up c. OutOfMemoryError will be thrown Only when OutOfMemoryError is thrown, most of us start to look at our application's memory settings. This is like only when a patient goes to... Continue Reading →
We had an outage in our online application GCeasy on Monday morning (PST) Oct' 11, 2021. When customers uploaded their Garbage Collection logs for analysis, the application was returning HTTP 504 error. HTTP 504 status code indicates that transactions are timing out. In this post, we would like to document our journey to identify the... Continue Reading →
Lets understand how GCeasy & yCrash differ from each other in the following table. GCeasyyCrashWhat is the purpose?GCeasy is used to optimize Garbage collection pause times & throughput.yCrash is an end-end root cause analysis solution. It answers the questions: Why did your application slow down? Why did the CPU spike up? Which objects in memory... Continue Reading →
