M/M/1 Queue Calculator

JJ Ben-Joseph headshot JJ Ben-Joseph

Queueing theory helps explain how a single server behaves when arrivals are random and service times are unpredictable. The M/M/1 model is the classic one-server queue: Poisson arrivals, exponential service times, and only one item being processed at a time. This calculator turns your arrival rate λ and service rate μ into the standard steady-state measures so you can judge whether a help desk, checkout lane, printer, or API worker is comfortably coping with demand or sliding toward congestion.

M/M/1 inputs: What you enter (and units)

For an M/M/1 queue, you only need two rates, and both must use the same time unit.

Important: If λ is per hour, μ must also be per hour. The waiting-time outputs, W and Wq, come back in that same unit, so an hourly input will produce hour-based averages that you can convert to minutes if needed.

M/M/1 stability condition (when the formulas apply)

The steady-state M/M/1 formulas only make sense when the single server can keep up on average.

If arrival pressure reaches or exceeds service capacity, the queue never settles into a stable long-run average. In that case, L, Lq, W, and Wq stop being useful as steady-state estimates because the line keeps growing instead of balancing out.

M/M/1 formulas and relationships

For an M/M/1 queue, the calculator starts with utilization, which shows what fraction of time the server is busy.

From ρ, the standard M/M/1 results follow:

The relationships:

These identities are all equivalent ways of reading the same queue. The forms with ρ are intuitive for congestion, while W = 1 / (μ - λ) and Wq = λ / (μ(μ - λ)) make it easy to see why delay rises sharply when arrival and service rates move close together.

The MathML below restates the same relationships for unambiguous rendering.

M/M/1 MathML (for unambiguous rendering)

ρ = λ μ , L = ρ 1 - ρ , W = L λ

How to interpret your M/M/1 queue results

Because the M/M/1 formulas are nonlinear, a small improvement in μ or a small reduction in λ can have an outsized effect once utilization is already high. That makes this calculator especially useful for comparing staffing or throughput changes before you commit to them.

Worked example: an M/M/1 help desk under moderate load

Here is a simple M/M/1 example using a single help-desk agent that receives about 5 requests per hour and can complete about 7 per hour.

1) Utilization:

2) Average number in system:

3) Average number waiting:

4) Average time in system and in queue:

A quick consistency check is that the mean service time is 1/μ = 1/7 hour ≈ 8.6 minutes. Adding that service time to Wq gives W, which is why the total time in system comes out to roughly 30 minutes.

M/M/1 formula summary table

Metric Meaning Expression (M/M/1)
ρ Utilization (busy fraction) λ/μ
L Avg. number in system ρ/(1-ρ)
Lq Avg. number waiting ρ²/(1-ρ)
W Avg. time in system L/λ = 1/(μ-λ)
Wq Avg. waiting time Lq/λ = λ / (μ(μ-λ))

Assumptions and limitations of the M/M/1 model

Historical note: Where the M/M/1 model came from

The M/M/1 model grew out of early telephone-traffic studies, where engineers needed a simple way to estimate how a single operator or line would behave under random call arrivals. The same idea still matters whenever one server has to absorb unpredictable demand, from contact centers to web services and small production lines.

Privacy: Calculations stay in your browser, so the M/M/1 rates you enter are not sent to a server by default.

How to use this M/M/1 queue calculator

  1. Enter Arrival Rate λ using the unit or time period you want to model.
  2. Enter Service Rate μ using that same unit so arrival pressure and service capacity are comparable.
  3. Run the calculation, then try a second λ/μ pair to see how the M/M/1 wait changes before you make staffing or throughput decisions.

Arcade Mini-Game: M/M/1 Queue Balance Challenge

Use this quick arcade run to practice spotting M/M/1 inputs that keep service ahead of arrivals before you trust the queue results.

Score: 0 Timer: 30s Best: 0

Start the game, then use your pointer or arrow keys to catch stable arrival-service pairs and avoid mismatched rates.

Enter λ and μ to see M/M/1 queue metrics.