[Operational] WAL Cleanup

[atroyn]

WAL Cleanup

The WAL grows unbounded, which can cause performance degradation on developer-class machines, especially on use-cases with dynamic data (which we are particularly focused on supporting): #2143

There are tools to clean this up but they shouldn’t be needed by default. Ideally the default developer should have no awareness of this at all.

API Design

TBA

[Complexity] Subtask

• [Unknown] Integrate tooling to clean up the WAL by user triggering.
• [Unknown] Automatically clean up the WAL with sensible defaults.
• [Unknown] Clean up the WAL in a resource-aware way.

[codetheweb]

Closed by the #2519 stack.