Queue Depth Calculator

Calculate M/M/1 and M/M/c queueing metrics: queue length, wait times, utilization, and Erlang C probability.

Use the Queue Depth Calculator

Queue Parameters

Metric Reference

Symbol Name Meaning
λArrival rateCustomers arriving per time unit (Poisson process).
μService rateCustomers one server completes per time unit (exponential service times).
cServersNumber of parallel identical servers.
ρTraffic intensityλ / μ. Total offered load. Must be < c for a stable queue.
uUtilizationρ / c. Fraction of time each server is busy. Must be < 1.
P0Idle probabilityProbability the system has zero customers.
C(c,ρ)Erlang CProbability an arriving customer waits (all c servers busy).
LqQueue lengthAverage number of customers waiting in the queue (not being served).
LSystem lengthAverage total customers in the system: Lq + ρ (Little's Law: L = λ × W).
WqQueue waitAverage time a customer spends waiting before service begins.
WSystem timeAverage time in the system: Wq + 1/μ. (Little's Law: W = L / λ).

Summary

Queue Depth Calculator applies M/M/1 (single-server) and M/M/c (multi-server) queueing theory models to compute steady-state queue metrics from three inputs: arrival rate (λ), service rate (μ), and number of servers (c). Results include traffic intensity, server utilization, average number of customers in queue (Lq) and system (L), average wait time in queue (Wq) and system (W), probability of empty system (P0), and Erlang C — the probability all servers are busy. A utilization ≥ 1 means the queue grows without bound.

How it works

  1. Enter the arrival rate (λ) in customers per second (or per minute).
  2. Enter the service rate (μ) — how many customers one server handles per the same time unit.
  3. Set the number of servers (c) to 1 for M/M/1 or higher for M/M/c.
  4. The calculator computes traffic intensity ρ = λ/μ and server utilization u = ρ/c.
  5. If utilization ≥ 1 the queue is unstable; a warning is shown and infinite-queue metrics are not defined.
  6. For stable queues, Erlang C gives P(waiting) and all Lq, L, Wq, W metrics follow from Little's Law.

Use cases

  • Capacity planning: find how many worker threads or pods are needed to keep wait time under a target SLA.
  • Database connection pool sizing: compute queue buildup when request rate approaches pool capacity.
  • Call center staffing: model agent count versus caller wait time using Erlang C.
  • Message queue monitoring: set alert thresholds for Lq before latency degrades.
  • Cloud autoscaling policy: determine the utilization trigger point where adding a server halves queue length.

Frequently Asked Questions

Last updated: 2026-06-19 · Reviewed by Nham Vu