pub fn set_compute_spill_enabled(enabled: bool)Expand description
Enable or disable chunk spilling on behalf of compute’s arrangement batchers.
Chunks carry no subsystem identity, so the spill decision is process-wide: committed chunks spill while either the compute or the storage gate is set. Each subsystem’s config application writes only its own gate, so the two dyncfg flags compose as an OR instead of clobbering each other.
Takes effect at the next settle. Already-spilled chunks are unaffected
either way. The pool is resolved per commit through
crate::pool_config::active_pool, so chunks spill only once
apply_pool_config has installed and budgeted the pool. With no pool
installed chunks stay resident regardless of the gates.