Don't Interrupt an Interrupt

Problem: The pattern Interrupts Unjam Blocking is causing people to thrash.

Context:

Execution of pattern for Interrupts Unjam Blocking.

Forces:

One worker will inevitably be blocked on you--you can't do both things at once.

Complete, omniscient foresight and scheduling are unreasonable.

Solution:

If a role is about to block on a critical resource, interrupt the role that provides that resource so they stop what they're doing to keep you unblocked.

If the overhead is small enough, it doesn't affect throughput. It will always improve local latency.

Resulting Context:

Largely unchanged from that emanating from Interrupts Unjam Blocking.

Design Rationale:

This is a simple, though somewhat arbitrary, rule to keep scheduling from becoming an elaborate ceremony.

Next: Compensate Success