What’s your mcRate!!

What's your Error budget? How reliable your site is? What's your application performance matrix? These questions hit to all Engineering Managers at some point in post-production operation space. To build a site that can satisfy end users, always check your system's #mcRate - Memory CPU Response Apdex Throughput Error

Memory Utilization -- High rates of memory utilization may indicate that processes are paging instruction sets out of virtual memory. Such paging leads to slower memory read times. The result is decreased performance for the associated application processes.

CPU Utilization -- CPU utilization is the sum of work handled by a Central Processing Unit. When the CPU hits 100% it can no longer process more work and application throughput flattens. Usually, a best practice would be to avoid 80% CPU utilization for each processor for long periods of time.

Response Time -- From end user’s perspective, application performance is the response time. Response time is the average time it took to generate the response to all requests. The response time is affected by factors such as network bandwidth, number of users, number and type of requests submitted, and average think time.

Apdex Score -- Response time needs to be translated into something meaningful as Apdex (The Application Performance Index) is an industry standard to measure users' satisfaction with the response time of web applications and services. Apdex is a measure of response time based against a set threshold. It measures the ratio of satisfactory response times to unsatisfactory response times. An Apdex score varies from 0 to 1. 

Throughput -- Total number of requests/responses processed by your application/service in relation to time. Transaction per second or minute.

Error Rate -- The application error rate is the number of requests that result in an error per time unit OR percentage of requests processed by application that generate an error.