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!
ConFoo.CA Developer Conference is one of the biggest conferences for programmers, that took place in Canada. For this year, ConFoo is going 100% virtual having more than 100 presentations by popular international speakers focused on pragmatic solutions for the software developers all over the world.
Continue reading “Confoo – 7 JVM Arguments”
In the series of chaos engineering articles, we have been learning to simulate various performance problems. In this post, let’s discuss how to simulate ‘java.lang.OutOfMemoryError: Java Heap space’ problem. This ‘java.lang.OutOfMemoryError: Java Heap space’ will be thrown by the application when the application generates more objects than the allocated heap size.
Continue reading “Chaos Engineering – Simulating OutOfMemoryError”
Java applications tend to contain hundreds (sometimes thousands) of threads. The majority of these threads are in WAITING, TIMED_WAITING (i.e., dormant) state, while only a small portion of the threads are actively executing lines of code. So, we were curious to know whether dormant threads consume less memory than active threads.
To figure out an answer to this question, we conducted a small study. Our findings were interesting, thus sharing with you.
Continue reading “Java threads – may not be memory efficient?”
In this series of chaos engineering articles, let’s discuss how to simulate CPU consumption to spike up to 100% on a host (or container). CPU consumption will spike up whenever a thread goes on an infinite loop. Here is a sample program from the open-source BuggyApp application, which would cause the CPU to spike up.
Continue reading “Chaos Engineering – Simulating CPU spike”
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?”
There are different options to terminate a process in Unix/Linux flavour of operating systems. This article intends to list down those options.
Continue reading “How to kill process in Unix/Linux?”Coming soon…
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’?”
‘Load Average‘ is an age-old metric reported in various operating systems. It’s often assumed as a metric to indicate the CPU demand only. However, it is not the case. ‘Load Average’ not only indicates CPU demand, but also the I/O demand (i.e., network read/write, file read/write, disk read/write). To prove this theory, we conducted this simple case study.
Continue reading “Load Average – indicator for CPU demand only?”
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’”
English
Arabic
Chinese (Simplified)
Dutch
French
German
Hindi
Italian
Portuguese
Russian
Spanish
Tamil