liveBook · Manning

Resource contention

Resource contention is competition among concurrent operations, processes, or workloads for access to a limited shared resource.

How 3 Manning books explain it

Latency

Resource contention is competition among concurrent operations or workloads for a limited shared resource, causing some to wait.

How it is used
Explains why shared hardware and synchronization points can raise latency as concurrent demand grows.
How deep it goes
Works through VM sharing, lock waiting, benchmark timings, and partitioning trade-offs without specifying a universal contention threshold.
Examples
Uses competing VMs, a mutex-protected counter, and an API server handling 1,000 requests per second.
What you can do after
Diagnose/debug with it by measuring latency as concurrency changes and checking for shared locks, noisy neighbors, or hot partitions.

Read how Latency explains resource contention →

C++ Concurrency in Action, Second Edition

Thread contention is competition among threads for access to shared data, a resource, or a synchronization primitive.

How it is used
Uses contention to reason about multithreaded performance and guide data-structure and work-queue design.
How deep it goes
Explains waiting, cache transfers, and cache ping-pong, then discusses layout and queue designs that reduce contention.
Examples
Uses a shared atomic counter, a mutex loop, per-thread work queues, and a shared stack of pending work.
What you can do after
Diagnose performance risks by identifying shared counters, mutex loops, queues, and stacks that can become contended.

Read how C++ Concurrency in Action, Second Edition explains resource contention →

Kubernetes for Developers

Resource contention is competition among workloads for finite computing resources on shared infrastructure.

How it is used
Explains how Kubernetes preserves node operation when Pods compete for finite CPU or memory.
How deep it goes
Connects requests, limits, QoS, priority, eviction, and rescheduling, but stops short of detailed capacity-sizing procedures.
Examples
Uses timeserver Deployments, CPU and memory settings, QoS classes, eviction-order figures, and priority-class YAML.
What you can do after
Diagnose frequent evictions and configure requests, limits, QoS, priority, and cluster capacity accordingly.

Read how Kubernetes for Developers explains resource contention →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.