Perform analysis
Continuously collecting and reviewing metrics on all the different components of the architecture is of paramount importance to determining possible issues, being able to differentiate aberrations from baseline operation and empirically evaluating the success of a deployed fix or the impact of a new feature.
The biggest challenge in analysis is determining what to analyze. Collecting data on "the standard" (CPU, memory, interrupts, network activity, load) metrics is always important. While those metrics are very useful, they rarely tie back to business objectives and are difficult to use to determine if you have achieved a specifically defined goal.
Defining metrics based on the established goal is of vital importance to demonstrating success. Additionally, these metrics are useful in achieving the more macroscopic objective: "once a goal, always a goal." By maintaining these metrics, one can ensure that future efforts or conditions do not lose a battle previously considered won.
Next: Achieve Goals →
Scalability & Performance Process
Opinion
OmniTI are the most professional and impressive people we have ever worked with, and we have always been able to depend on them.
~ Aaron Kalsnes, Co-founder, TeenSpot.com.
