In Unix/Linux operating systems, processes can be in one of the following states:
1. RUNNING & RUNNABLE
2. INTERRRUPTABLE_SLEEP
3. UNINTERRUPTABLE_SLEEP
4. STOPPED
5. ZOMBIE
Let’s discuss these states in this article.
Continue reading “What are the process states in Unix/Linux?”
Load average is an age-old metric, which is in existence since the 1970s to indicate whether the system is under heavy/average/low load. It is useful to indicate whether the system’s load is on an increasing trend or a decreasing trend. In this article, let’s learn more about ‘Load Average’.
Continue reading “What is ‘Load Average’?”
CPU consumption in Unix/Linux operating systems are studied using 8 different metrics: User CPU time, System CPU time, nice CPU time, Idle CPU time, Waiting CPU time, Hardware Interrupt CPU time, Software Interrupt CPU time, Stolen CPU time. Let’s review each of the CPU time in this article.
Continue reading “Different CPU times – Unix/Linux ‘top’”Lets understand how GCeasy & yCrash differ from each other in the following table.
Continue reading “What is the difference between GCeasy and yCrash?”
When you are running your Java application in physical servers, you would have been using ‘-Xmx’ JVM argument to specify the Java heap size. If you are porting your application to Containers, you might be wondering how to configure Java heap size in the container’s world? Are there any best practices? In this article, we will discuss the possible JVM arguments that can be used to specify the Java heap size and the best option to choose.
Continue reading “Best practices: Java memory arguments for Containers”
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!
Buggy App is a simple java application that simulates different performance problems like Memory Leak, OutOfMemoryError, CPU spike, thread leak, StackOverflowError, deadlock, unresponsiveness, …
Continue reading “Buggy App – Simulate performance problems”
yCrash provides a safe and secure mechanism to troubleshoot production problems. In this article, let’s discuss about the safety measures provided by yCrash.
Continue reading “yCrash – safe and secure way to troubleshoot”
yCrash is our end-end root cause analysis solution built on top of our successful products GCeasy, fastThread, HeapHero. yCrash leverages the same underlying parsing engine and ML algorithms of these 3 tools. On top of it, yCrash provides additional capabilities. This document intends to highlight those key capabilities.
Continue reading “GCeasy + fastThread + HeapHero + lot more … = yCrash”
yCrash has two components:
Below are the steps to install them.
Continue reading “yCrash Installation”
