Glossary · System coordination, integration and orchestration
Resource contention
Also known as: Contention
German: Ressourcenkonflikt
In automation and computing, resource contention is the situation in which several tasks, machines or processes compete for the same limited resource at the same time, which leads to waiting, reduced throughput or, without proper coordination, conflicts and deadlocks.
- System integration
In one sentence
Resource contention is competition of several tasks or machines for the same limited resource, causing waiting, lower throughput or deadlocks.
Example
Three stations share one camera inspection unit; at peak output, contention for the camera becomes the bottleneck of the line.
How it applies
- Engineering: Identify shared resources early and estimate their utilization. Contention can be reduced by adding capacity, reducing hold times, splitting resources or better scheduling.
- Operation: Contention shows up as waiting times at specific resources. Measure how long requesters wait, not only how busy the resource is.
- Software: In controllers and IT systems, contention for CPU, memory, network or database locks can cause missed cycle times or timeouts; monitor it as part of performance testing.
- Documentation: Describe known contention points and their effect on cycle time in the system description, so planners and service staff understand throughput limits.
Resource contention vs. deadlock
Contention means requesters wait, but eventually proceed. A Deadlock means two or more requesters wait for each other forever. Contention reduces performance; deadlock stops the system.