When a system spends all its effort swapping work in and out — and none doing it. Maximum activity. Zero progress.
Each task needs two folders open at once. The desk holds four. Do the arithmetic before you press the button — he can't. Past two tasks, watch the two meters part ways: effort pinned at the ceiling, progress flat on the floor. That divergence has a name, and it is stamped across the scene in red. The cabinet, for the record, is not getting any closer.
Thrash and thresh are the same word — rhythmic beating to separate wheat from chaff. Honest work, once. The flailing was the point, and the flailing produced food. Hold that thought.
By early modern English, to thrash is also just to flail — at an opponent, in water, in bed with fever. The motion survives; the wheat is gone. The word is already rehearsing its future.
Early time-sharing systems kept collapsing: load one program too many and throughput didn't dip — it fell off a cliff. Denning's working-set paper explains why. When memory is overcommitted, the machine spends its life swapping pages instead of running them. He calls it thrashing. The farm word, resurrected, for beating that yields no grain.
Virtual memory wins; thrashing becomes the canonical failure mode, the graph every student sees: utilization climbing, climbing — then vertical collapse. The lesson generalizes badly and beautifully: more load past saturation produces less of everything.
Linux ships the OOM killer: when memory runs out, the kernel selects a process and executes it, on the theory that a quick death beats a slow universal one. An operating system choosing murder over thrashing is the strongest insult ever paid to this word.
Cache lines ping-pong between cores. Threads convoy on a lock. And the human version: six urgent tasks, four slots of attention, every context switch evicting the thing you just reloaded. Task-switching research keeps measuring the same cliff Denning drew. Your desk is RAM. It was always RAM.
An agent re-reading the same file for the ninth time, re-running the same failing tool, swapping context in and out of a window too small for the problem — that's paging. The oldest failure mode in computing, freshly reborn, and still nobody's first guess. The word is ready. It never left.