memory leak

Tibco Business Events Memory leak analysis in live production

As a performance architect I get called into various production performance issues. One of our recent production issues happened with Tibco Business Event (BE) Service constantly violating our Service Level Agreements (SLA) after running 10-15 hours since the last restart. If we keep the services running for longer we would see them crash due to an “out of memory” execution. This is a typical sign of a classic memory leak! In this blog … read more

Analyzing out-of-memory exceptions caused by overly aggressive logging

As a performance architect I conduct many performance tests against Java Enterprise apps, analyzing performance, scalability and stability issues of the application under load. One of our recent tests was against an application that kept crashing with “Out of Memory Exceptions” whenever we ran our JMeter-based Load Tests. Typically, the first thought in such a case is usually: this is probably a memory leak! In this blog I’ll walk through the steps taken to analyze the … read more

How to track down CPU issues in Node.js

A running application is represented through some state stored in memory and calculations carried out by the CPU. Typically performance problems materialize in these two areas. In my last post I’ve explained garbage collection and how to hunt down memory problems in Node.js. In this blog post I’ll cover the CPU aspects of Node.js including the event loop and how to track down tasks that consume too much CPU time … read more

Understanding Garbage Collection and hunting Memory Leaks in Node.js

Whenever there is bad press coverage of Node.js, it is (typically) related to performance problems. This does not mean that Node.js is more prone to problems than other technologies – the user must simply be aware of certain things about how Node.js  works . While this technology has a rather flat learning curve, the machinery that keeps Node.js ticking is quite complex and you must understand it to preemptively avoid performance pitfalls. And if things go wrong … read more