---
title: Understanding Utilization - SCHILLER
description: 'Interactive simulation: Why 80% utilization causes exponentially growing
  wait times.'
url: https://ad-ze.de/en/understanding-utilization
language: en
---

# Understanding Utilization

## Why 80% Utilization Is a Problem

Experience interactively how queues really form

Whether servers, teams, or production lines — beyond a certain utilization level, wait times don't grow linearly but exponentially. What seems harmless at 50% becomes a real problem at 80%. Experience it yourself with our interactive simulation.

Move the slider, click Start and watch how the queue changes.

  Utilization (ρ)  
 50%  

 ▶ Start Reset 

 Speed: 0.5x 1x 2x 4x 

## Queue

Current

0

Running avg

-

Theory avg

-

Collecting data...

Served

0

Avg wait time

-

Checkout utilization

 50% 

## M/M/1 Theory Curve: Lq vs ρ

Lq = ρ² / (1 - ρ)

 Model Parameters (M/M/1) 

Service rate (μ)

μ = 1.00 (Exponentially distributed)

Arrival rate (λ)

λ = 0.50 (Poisson process)

Utilization (ρ = λ/μ)

ρ = 0.50

Theoretical results

 Lq = 0.50, L = 1.00 

M/M/1 Model: Single checkout (1 server) with Poisson arrivals and exponentially distributed service times. The variance in service time is crucial — some customers are fast, others slow.

## The Trap of Comfortable 80%

A seemingly good utilization of 80% leads to drastic queues. The jump from 50% to 80% increases the average queue length sixfold.

ρ = 50%

Lq = 0.5

ρ = 80%

Lq = 3.2

ρ = 90%

Lq = 8.1

ρ = 95%

Lq = 18.1

Keep utilization below 80%!

## Where does this happen in practice?

### The Overloaded Server

A server at 50% utilization responds almost instantly. At 80%, requests wait on average 3× longer. At 90%, it's 9×. Not because the server gets slower — but because requests pile up in front of it. What looks like a hardware problem from the outside is usually a utilization problem.

### The Emergency Room at Its Limit

A hospital at 95% bed occupancy has almost no buffer. A normal Monday with slightly more accidents than usual is enough to bring the entire emergency room to a standstill. Not because the staff works worse — but because the system has no slack left. Every fluctuation hits directly.

### The Machine as Bottleneck

A machine running at 80% has an average of 3 parts waiting in front of it. At 90%, it's already 8. The same applies to forklifts, packaging lines, and truck docks. Lean manufacturing deliberately builds in buffers — not out of waste, but as protection against these fluctuations.

### The Manager as Bottleneck

A manager with a full calendar can handle roughly one decision per day. At 80% calendar utilization, an average of 3 requests are already waiting — at 90%, it's 8. Investment requests, hiring decisions, escalations: everything lands in the same queue. The team stands still — even though the manager works non-stop.

 What does utilization (ρ) mean? 

Utilization ρ is the ratio of arrival rate (λ) to service rate (μ). It shows what fraction of a server's capacity is being used. At ρ = 0.5, a customer arrives while the server is still idle 50% of the time. At ρ = 0.9, the server is busy 90% of the time.

 Why does the queue keep dropping to 0 at 80%? 

That's not a bug! With ρ = 0.8, an empty queue is expected about 20% of the time (P(0) = 1 - ρ). The simulation shows the fluctuations — sometimes a customer arrives when the server happens to be free, sometimes queues build up. The running average approaches the theoretical value with more measurements. Queues breathe at high utilization!

 The math behind it 

The M/M/1 model (Markov/Markov/1 Server) describes a system with exponentially distributed arrival and service times. Key formulas: Mean queue length Lq = ρ²/(1-ρ), Mean wait time Wq = ρ/(μ(1-ρ)), Mean customers in system L = ρ/(1-ρ), Mean time in system W = 1/(μ-λ). Crucially: The denominator (1-ρ) causes all metrics to approach infinity as ρ approaches 1.

  ![Michael Schiller](https://ad-ze.de/rails/active_storage/representations/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NDcwMzksInB1ciI6ImJsb2JfaWQifX0=--2f16e9a9191c77e10117f2790eed35b6118222e1/eyJfcmFpbHMiOnsiZGF0YSI6eyJmb3JtYXQiOiJ3ZWJwIiwicmVzaXplX3RvX2ZpbGwiOlsyMDAsMjAwXSwic2F2ZXIiOnsic3RyaXAiOnRydWUsInF1YWxpdHkiOjUwLCJpbnRlcmxhY2UiOnRydWUsIm9wdGltaXplX2NvZGluZyI6dHJ1ZSwiYWNjZXNzIjoic2VxdWVudGlhbCIsImJhY2tncm91bmQiOlsyNTUsMjU1LDI1NV19fSwicHVyIjoidmFyaWF0aW9uIn19--ddadceab840027df8f77d653b1b35d2b9a4a053b/image.webp?locale=en) 

## Identify capacity problems before they arise

We help you identify bottlenecks in IT, processes, and teams — before they slow down your customers or employees.

 [Get in touch](https://ad-ze.de/en/get-in-touch?service=understanding_utilization) 

Request capacity consulting

 [Get in touch](https://ad-ze.de/en/get-in-touch?service=understanding_utilization)
