Queueing

Version

v2 · 2026-08-30 · History · 2 corrections

Prime #

169

Domain group

Formal Sciences

Origin domain

Operations Research

Also from

Mathematics, Computer Science & Software Engineering, Systems Thinking & Cybernetics

Aliases

Queueing Theory, Waiting Line Theory, Buffer

Related primes

Scheduling, Resource Management, throughput, little s law, Bottleneck

Core Idea

Queueing is the organization of tasks or entities into a waiting line for processing or service, often governed by rules like first-in-first-out (FIFO) or priority-based access.

How would you explain it like I'm…

Waiting in Line

When too many kids want one slide at the playground, you have to make a line. The slide can only take one kid at a time, so everyone waits their turn. The longer the line, the longer you wait. If too many kids show up too fast, the line gets really, really long.

Lines That Form for Service

Queueing is what happens when stuff waits to be served by something with limited capacity, like cars at a toll booth or people at a checkout. The line depends on how fast things arrive, how fast they can be served, and how many servers there are. There's also a rule for who goes first (usually whoever arrived first). One important thing: if a server is almost always busy, even small bursts make the line shoot up fast. That's why busy places feel so painful to wait at.

Waiting at a Limited Server

Queueing is the structured buildup of work items, customers, packets, cars, or jobs, waiting for service at a resource with limited capacity. To describe a queue you need to know the arrival pattern (how often things show up), the service pattern (how long each takes), the number of servers, and the queue discipline (first-in-first-out, priority, etc.). Queueing theory gives mathematical tools for predicting wait times and throughput. A key result, Little's law, says the average number in the system equals the arrival rate times the average wait time, regardless of discipline. Another key insight: as utilization approaches 100 percent, waiting time grows without bound, which is why busy systems feel disastrous even though everything technically still works.

 

Queueing is the structured accumulation of work items (requests, customers, packets, cars, patients, jobs) awaiting service at a resource with finite capacity, together with the rules (queue discipline: FIFO, LIFO, priority, random) and parameters (arrival process, service process, number of servers, buffer size) that determine how items wait, how long, and with what predictability. The mathematical analysis is queueing theory, which gives quantitative tools for predicting wait times, utilization, throughput, and loss under different workloads. Every queueing model specifies an arrival process (deterministic, Poisson, or general; rate lambda), a service process (deterministic, exponential, or general; rate mu per server), the number of servers and buffer capacity (notated in Kendall's notation as M/M/1, M/M/c, M/G/1, etc.), and a queue discipline (FIFO, LIFO, shortest-job-first, priority, processor-sharing, fair queueing). Little's law (L equals lambda times W) is a universal relationship between average number in system, arrival rate, and average time in system, independent of discipline. A critical practical fact: as utilization rho approaches 1, mean wait time diverges, producing queue explosion. Foundations include Erlang's telephone-traffic work (1909), Kendall's notation (1953), Little's law (1961), and Jackson networks (1957).

Tensions in Practice

• Arrival order in tension with short-job responsiveness

Cross-Domain Echoes

See how this entry connects to another domain.

• A wait can occupy more than the waiting item
• Waiting needs a consequence, not just a clock

Broad Use

• Operating Systems: Process scheduling queues, print queues, or network request queues.

• Retail: Customers forming a line at checkout.

• Traffic Management: Cars lining up at traffic signals or toll booths.

• Services: Call centers routing callers to available agents.

Clarity

Structures how resources (e.g., CPU time, cashier counters) serve tasks or requests in a transparent, orderly fashion.

Manages Complexity

Prevents chaotic contention for resources, establishing a predictable approach for handling surges in demand or limited service capacity.

Abstract Reasoning

Focuses on arrival rates, service rates, and queue discipline—helpful concepts in analyzing throughput, wait times, and bottlenecks.

Knowledge Transfer

Queueing logic applies to any scenario requiring fair or structured waiting, from network packet management to hospital triage.

Example

A BFS (Breadth-First Search) queue in graph algorithms mirrors people standing in line for a resource: one is served at a time, and new arrivals join the end of the queue.

Relationships to Other Abstractions

Current abstraction Queueing Prime

Parents (2) — outgoing typed relations

• Queueing is a kind of Allocation Prime

  Queueing is a kind of allocation that distributes finite service capacity across arriving demands by determining who waits and for how long.

• Queueing presupposes Flow Prime

  Queueing presupposes flow because waiting only arises when an inflow of work items meets a service capacity that constrains throughput.

Children (12) — abstractions linked here by typed relations

• Adversarial Queueing Network Domain-specific is a kind of Queueing

  The routed-packet model is a queueing-system model with constrained injections, edge waiting and specified service rules.

• BCMP network Domain-specific is a kind of Queueing

  Queueing (prime:queueing).

• Layered Queueing Network Domain-specific is a kind of Queueing

  A Layered Queueing Network is Queueing with nested service requests whose waiting and service times depend across layers.

• Offered load Domain-specific is a kind of Queueing

  Offered load instantiates Queueing because it compresses an arrival stream and service-time requirement into the mean work presented at a queueing resource before admission outcomes.

• Backorder Domain-specific includes Queueing

  Backorder contains a visible waiting line of accepted obligations that incoming resupply serves under an allocation discipline.

▸ Show 7 more

Hierarchy paths (2) — routes to 2 parentless roots

• Queueing → is a kind of Allocation → presupposes Scarcity → is a decomposition of Constraint

Show alternative path (1)

Not to Be Confused With

• Queueing is not Scheduling because Queueing characterizes the stochastic dynamics of waiting through arrival and service distributions (Kendall notation A/B/c), whereas Scheduling is the deterministic assignment of tasks to times and resources to minimize makespan or lateness.
• Queueing is not Chunking because Queueing models the waiting behavior of discrete items in a system with finite service capacity, whereas Chunking restructures information items into consolidated units to reduce cognitive load.
• Queueing is not Layering because Queueing describes the temporal flow and waiting of work items, whereas Layering is the architectural decomposition into horizontal strata with unidirectional dependencies.
• Queueing is not Pipeline because Queueing models the waiting phenomenon when demand exceeds capacity, whereas Pipeline is the staging of sequential steps allowing concurrent execution of items across different stages.