What is Interrupt Coalescing?

Interrupt Coalescing is a mental model used for better thinking and decision-making.

How do you apply Interrupt Coalescing?

To apply Interrupt Coalescing, identify situations where this framework is relevant, then use it as a lens to evaluate your options and decisions. The model is most useful when combined with other complementary mental models.

What category does Interrupt Coalescing fall under?

Interrupt Coalescing falls under the Computer Science & Algorithms category of mental models. Other models in this category can be found on the Computer Science & Algorithms hub page.

Why is Interrupt Coalescing important?

Interrupt Coalescing is important because it provides a structured way to think about problems that would otherwise be approached with intuition alone. Understanding this model helps you avoid common reasoning errors and make better decisions.

Interrupt Coalescing Mental Model…

Interrupt Coalescing Mental Model… | Faster Than Normal

Section 2

How to See It

Systems

You're seeing Interrupt Coalescing when a NIC or driver aggregates packet arrivals and delivers one interrupt per N packets or per time window, reducing context switches and improving throughput under load.

Operations

You're seeing the same idea when a team batches notifications, status checks, or approvals (e.g. "digest every 4 hours" or "review in batches") instead of reacting to every single event. Fewer context switches; more focus and throughput.

Section 3

How to Use It

When handling many small events is costly (context switches, overhead), batch them: wait for a time window or a count threshold, then process together. Accept a bounded increase in latency for a large gain in throughput. Tune the coalescing window to your latency vs. throughput requirements.

Decision filter

"Are we reacting to every event immediately? If the cost of reacting is high and events are frequent, should we coalesce — batch by time or count — and trade a bit of latency for much higher throughput?"

As a founder

Apply coalescing to operations: batch standups, notifications, or reviews instead of real-time reaction to every message or ticket. Define a "coalescing window" (e.g. "we triage twice daily") so the team gets focus time and still meets latency expectations.

Section 5

Founders & Leaders

Reed HastingsCo-founder & CEO, Netflix

Netflix batches content delivery and product decisions (e.g. full-season drops, focused roadmap cycles) rather than reacting to every signal. Hastings has emphasised context over control and reducing unnecessary interruptions so teams can execute. Founders can apply the same pattern — defined windows for messages, reviews, and meetings — to increase throughput of real work.

Section 7

Connected Models

Reinforces

Batching

Batching is the general principle: group similar work and do it together to reduce setup cost and context switching. Interrupt coalescing is batching applied to interrupts; the same idea applies to tasks, messages, and reviews.

Tension

Latency

Coalescing increases worst-case latency (you wait for the batch). When latency is critical (real-time control, safety), coalesce less or not at all. The tension is throughput vs. responsiveness; choose the coalescing window to match SLA.

Leads-to

Throughput

The goal of interrupt coalescing is higher throughput: more useful work per unit time by reducing overhead. It leads to the broader question — where else can we batch to increase throughput without breaking latency guarantees?

Section 8

One Key Quote

"Batch the interrupt; spare the context switch."
— Systems design principle

Section 11

Summary & Further Reading

Interrupt coalescing batches interrupt handling to reduce context switches and raise throughput at the cost of some latency. Use the same idea in operations: batch notifications, reviews, and communication so that focus and throughput increase while latency stays within bounds.

Interrupt Coalescing — Linux and NIC documentation

Reference

How operating systems and drivers implement interrupt coalescing and tune it.

Deep Work — Cal Newport (2016)

Book

Batching interruptions and communication to protect focus and throughput; human-side coalescing.

The Phoenix Project — Kim et al. (2013)

Book

Operations and flow; batching work and reducing context switching in delivery and support.

Interrupt Coalescing

Continue exploring

Popular Mental Models

Core Idea

How to See It

How to Use It

Founders & Leaders

Connected Models

One Key Quote

Summary & Further Reading

This connects to...

Continue exploring

Popular Mental Models

More like this, in your inbox

Core Idea

How to See It

How to Use It

Founders & Leaders

Connected Models

One Key Quote

Summary & Further Reading

This connects to...