Skip to content

Prefer memory bound to CPU bound if a worker is both

Sean McGivern requested to merge docs-clarify-resource-boundaries into master

If a worker needs lots of CPU and memory, it should be marked as memory-bound:

  1. Memory-bound jobs already run with low concurrency, which means they have more CPU time available anyway.
  2. We forbid latency-sensitive memory-bound jobs, but not latency-sensitive CPU-bound jobs, so if a job is both, we should make sure it trips that switch.

Closes #207186 (closed).

Edited by 🤖 GitLab Bot 🤖

Merge request reports