Avoiding performance bottlenecks

Over the last few sections, we took a look at the different ways we can profile our application for different kinds of performance bottlenecks that may involve slowdowns to memory leaks. But once we're aware of these issues and why they're happening, what other options do we have to prevent them from occurring again?

Fortunately, we have a couple of helpful guidelines that may help prevent performance bottlenecks or can limit the possible impact of these bottlenecks. So, let's take a look at some of these guidelines:

• Choosing the correct design patterns: Design patterns are an important choice in the application. For example, a logging object doesn't need to be reinitialized in every submodule of the application and can easily be reused as a global object or a shared object. Making a logging class a singleton can help us in this.
• Cleaning up the objects as soon as they go out of scope: As a developer, we need to take care of cleaning up the objects as soon...