Optimize Your Code

Cost vs risk of leaking code

Source code leaking or hogging resources is a nightmare for any organization and developers alike. Be it an application which crashes randomly due to unusually high memory consumption or any software which hogs CPU and starves other applications to death, these are perfect recipes for disaster for any organization.

Poorly written working code can often be far worse than non-functional code as it can lead to catastrophic side effects.  It is a double-edged sword as it not only eats up system resources and hampers its performance, at the same time it adds up an entry in terms of cost for problem determination, defect resolution, research, operational and support costs.

How costly is leaking code?

continue reading…

Do you see the dreaded ‘OutOfMemoryError’ while running your Java application? Does it crash every now and then? Does it have memory leaks? Is your

Memory leaks

application slowing down the operating system significantly? Is your application taking forever to execute? Developers are often left pondering over these questions while writing Java applications. So, what are memory leaks? What causes them? How can you fix them in your Java applications?

In the first post of this series, we walk you through the relevant details to understand memory leaks in Java. The later posts of this series will focus on how to detect and fix memory leaks in Java applications.

What are memory leaks?

continue reading…