Performance Analysis

When evaluating web service response times, why is the 99th percentile (the boundary of the slowest 1%) often examined in addition to the mean?

  1. AThe mean can look good while some requests are very slow, and when a task waits on many components, those slow responses set overall latency
  2. BThe 99th percentile is always smaller than the mean
  3. CThe mean cannot be calculated
Show answer and explanation

Answer: A. The mean can look good while some requests are very slow, and when a task waits on many components, those slow responses set overall latency

Response-time distributions tend to be mostly fast with a small, very slow tail. Looking only at the mean hides that tail. Moreover, when rendering a page waits on 100 components, any one slow response makes the whole slow, so the slowest 1% affects most users. Systems are therefore managed against targets for the slow end (tail latency).

  • A. Correct. This is called tail latency.
  • B. Being on the slow side, it is usually larger than the mean.
  • C. The mean can be computed but is insufficient alone.
Practice this topic Back to topic

More Performance Analysis questions

  1. A server receives 100 requests per second, each taking 0.2 seconds on average (steady state). How many requests are in progress at once on average (Little's law)?
  2. What happens to request waiting time as server utilization (fraction of busy time) approaches 100%?
  3. What is the purpose of using a profiler when improving program performance?
  4. What characterizes a sampling profiler?
  5. Which statement about instrumentation profilers, which insert timing code at function entries and exits, is correct?