-
Let them talk
On our quest to solve every memory leak in the Java world we get in touch with many teams who struggle with performance issues of their applications. Every developer tries to solve these differently. Some begin with vmstat or top, others with a CPU profiler or a DB load monitoring tool. Many of them turn to different APM products, like CA APM, AppDynamics, dynaTrace, etc. However, if you properly ask the application, it will normally give you all the information you need for performance tuning. And you can get the info without relying on indirect metrics of the operating system or the JVM.
Filed under: Performance
-
Announcing bugfix release 1.0RC2
First of all a big thanks to everyone who rushed in over the last days - the first public version of Plumbr turned out to be extremely popular! Thanks for keeping us up the days and nights, collecting feedback and improving the product. And the result is here - we just released Plumbr 1.0RC2. It slightly improves leak detection and the leak report, and fixes the bugs that have been discovered - and is a step closer to a generally approved 1.0! We encourage everyone to upgrade.
Filed under: Product Updates
-
Put your fat Collections on a diet!
Java Collection API is one of the most used APIs in the Java world. It provides a convenient and pretty solid way to implement and use some every-day data structures. But are they suitable and efficient in all situations? In this article I will investigate one case from our own experience where Java Collection API turned out to be a huge waste of memory in a pretty trivial usage scenario.
Filed under: Memory Leaks
-
Public beta is now released. Welcome aboard!
Starting from today, the memory leak detector Plumbr is available to everyone as a public beta. This release marks a major milestone for us. After months of development we can now proudly present the first public release!
Filed under: Product Updates
-
Solving OutOfMemoryError (part 3) – where do you start?
How do I know that the application is actually suffering from memory leaks? Where and how can I find the cause of the possible memory leak? An experienced developer usually begins its troubleshooting by answering the aforementiond fundamental questions.
Filed under: Memory Leaks
-
Solving OutOfMemoryError (part 2)- why didn’t operations solve it?
You are a developer. You should not be solving problems occurring in production once in a blue moon. But here you are again, trying to figure out what has gone wrong again. Why are you here and what could be done differently to avoid you solving these problems? After all - your operations is also full of competent people. They have tried their best to pinpoint the root cause, by pulling different tricks from their book of knowledge. What we have faced is that the methods used might not always be the most beneficial.
Filed under: Memory Leaks
-
Solving OutOfMemoryError (part 1) – story of a developer
Another day in the office. Except that you get another call from the operations saying they now have to restart your production application every three hours. And they seem to be somewhat annoyed with this. You have a feeling that their emotion is in correlation to the number of phone calls customer support is getting lately - which has skyrocketed in the past few weeks.
Filed under: Memory Leaks
