Size. Lifetime. Deadline.
Every request tells you how much space it needs, how long it stays, and how quickly it must be placed.
Field guide
Keep useful space alive.
Requests need contiguous cells and must be placed before their deadlines. The blocks you place eventually finish and release their cells—but their sizes and lifetimes determine what gaps they leave behind.
Choose the future shape.
Tap a request, then choose a valid start or end of a gap. Nearby lifetimes matter as much as empty space.
Let finished work clear.
Processes count down and release automatically. Group similar lifetimes to build useful openings.
Prepare for pressure waves.
Calm intervals give way to warnings and allocation storms. Use recovery time to rebuild a clean layout.
Move memory at a cost.
Compaction closes gaps, but consumes limited charges and advances time while requests continue waiting.
Respect pins and leaks.
Pinned processes do not move during compaction. Leaks persist until a scenario provides another answer.
Understand the pressure