yCrash app is a non-intrusive, secure, instant root cause analysis tool. It captures thread dump, heap dump, GC log, netstat, vmstat, top, and several more artifacts, right when the problem is happening in the production. It instantly analyzes all the artifacts & generates a root cause analysis report in the dashboard. Watch this below video clip to get a detailed overview of yCrash!
Hi Friends! This is all about our yCrash Team having a fun time together. Before explaining how our trip goes, We are dedicating a short poem.
Continue reading “Work Together, We get ‘together’”
JAX – Online conference is the meeting place for all Java and software architecture enthusiasts! This year also, they have conducted an online conference to exchange knowledge and ideas from speakers all over the world.
Continue reading “Let’s crash the applications! – W-JAX 2021”
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”
Spring pet clinic application is a sample application developed by the Spring Framework developers to demonstrate the capabilities of Spring Boot, Spring MVC and Spring Data Framework. We set out to conduct a performance test on this application and see whether we can identify any performance bottlenecks.
Continue reading “Spring Boot pet clinic app – performance study”
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 a critical condition; we begin to give treatment :-).
In this post, let’s discuss how to detect whether your application’s memory is under-allocated or not in a proactive manner.
Continue reading “Detect proactively whether application’s memory is under-allocated”
As the author of GCeasy – Garbage collection log analysis tool, I get to see few interesting Garbage Collection Patterns again & again. Based on the Garbage collection pattern, you can detect the health and performance characteristics of the application instantly. In this post, let me share few interesting Garbage collection patterns that have intrigued me.
Continue reading “Interesting Garbage Collection Patterns”
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 root cause of the problem.
Continue reading “AWS Cloud watch + yCrash = Monitoring + RCA”
‘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()”
I am slightly hesitant to write this post, as it might attract some criticism. Nevertheless, I told myself there is nothing wrong with sharing my point of view (even though it might not be well accepted). I would like to share my personal experience regarding yesterday’s Monolithic and today’s Microservice architecture in this post.
Continue reading “Is today’s microservice more bloated than yesterday’s monolith?”
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”
English
Arabic
Chinese (Simplified)
Dutch
French
German
Hindi
Italian
Portuguese
Russian
Spanish
Tamil