What makes an application perform optimally? I would say it is when there is collaborative performance from the server or the VM running the application, the network on which the application is used, and the storage. In this post, I provide information regarding storage and ways to configure it to avoid application performance bottlenecks.

 

LUN contention

LUN contention is the most common issue that storage admins try to avoid. Here are a few common mistakes that usually lead to LUN contention:

  • Deploying a new application on the same volume that handles busy systems, such as email, ERP, etc.
  • Using the same drives for applications with high IOPS.
  • Configuring many VMs on the same datastore.
  • Not matching storage drivers with processors.

Application issues can be traced to LUN contention only if the concerned database is being monitored. Drilling down to the appropriate LUN helps you make sure that the application runs fine.

 

Capacity planning

Poor application performance often can be tied to increased demand for services, and many times it can be storage and its IOPS. Storage is costly, and no organization wants to waste it on applications.

Capacity planning involves knowing your application, how much space it needs, and the kind of storage it requires. Capacity planning helps in predictive analytics, which allows users to choose the amount of storage their application requires. Capacity planning should be done before the application is moved into production. Doing so not only helps to right-size the application’s storage environments, but eventually helps lower the number of performance issues an application might experience during rollout.

 

Make sure it’s not the storage

SysAdmins often blame storage for application performance issues. It is always recommended to monitor your storage, which helps eliminate the blame game. Monitoring your storage helps you see whether it’s actually storage that’s causing performance issues, rather than the server or the network itself. Continuously monitoring your database can also help you avoid LUN contention. You will also be able to monitor the performance of your capacity planning, and be alerted when it’s not performing optimally.

Storage is the lowest common denominator of application monitoring. Application stack monitoring allows you to troubleshoot issues from the application itself. Consider the following troubleshooting checklist, and ask yourself:

  • Is it the application itself?
  • Is it the server on which the application is hosted?
  • Is it the VM?
  • Is it the storage?

I will walk you through the different layers and how they help troubleshoot application issues in my next blog. Also, to find out more about App stack monitoring, please visit us at booth HH18 at this year’s IP Expo in London.