Oracle should increase batched sizes based on load.

One way to speed up the oracle during busy periods is to increase the batch sizes while it's being hammered and decrease them again during periods of no load.

Locate the Oracle implementation and its existing batch-size handling, then read how load or busy and idle periods are represented. Define how batch sizes should increase and decrease, including bounds and timing, before identifying the relevant tests. Done means the Oracle adapts its batch size under load and returns to a smaller size when idle, with tests covering both transitions.

Written by the indexing model from the issue text.