Serial update queue saturation with concurrent $set in Svelte components

Answer

The serial update queue is the intended behavior for all component trees in Svelte 4.x; there is no exposed flag to switch to a batched model, and batching is only under discussion for future releases (e.g., Svelte 5.x).

Confirmed facts

• $set calls are processed one after another in a serial microtask queue.
• Each $set triggers a DOM update, after which the tick() promise resolves as a separate microtask.
• tick() callbacks are neither cancellable nor coalesced; they fire once per update cycle.

Likely explanation

The scheduler chooses serial processing to keep reactivity deterministic and to avoid complex interleaving of state changes; introducing batching would require a redesign of the update loop and could affect existing semantics.

Steps to reason about latency

1. Wrap each $set call with performance.now() before and after, recording the delta.
2. If you have access to Svelte’s internal debug API (e.g., component.$$._dirty), log its length to see how many updates are pending.
3. Aggregate the deltas to estimate average latency per component under concurrent load.
4. If microtask overhead becomes a concern, consider debouncing or grouping $set calls manually, noting that this changes reactivity semantics.

Missing diagnostic detail

Which Svelte version are you targeting (4.x or 5.x)? This determines whether a batched update model is currently available or only planned.