test: reduce mutation observer delay from 200ms to 0ms#13642
Conversation
Experimental change to measure CI test execution speed impact. In Render.ts, the mutation observer timer waits 200ms before resolving the render task promise. This commit reduces it to 0ms to evaluate whether tests run faster on CI.
|
🚀 Deployed on https://pr-13642--ui5-webcomponents-preview.netlify.app |
Finding: no measurable speedupCompared the Test step durations on the same passing jobs in this PR (0ms) vs baseline run #26949481414 on main (
Total across these five passing jobs: 773s (PR) vs 778s (main) — a 5-second / ~0.6% delta scattered in both directions, well within run-to-run noise. Why the 200ms doesn't actually cost 200ms per testThe mutation-observer timer in
So the 200ms is a "settle" guard, not a per-render wait. Closing this — the speedup hypothesis didn't hold. Better targets if chasing test-speed wins
|
|
Closing — see comment above for the finding. The 200ms mutation-observer delay isn't a meaningful contributor to test duration. |
Purpose
Experimental PR to measure the impact of the mutation observer delay on CI test execution speed.
Change
In
packages/base/src/Render.ts, the mutation observer timer inscheduleRenderTaskcurrently waits 200ms before resolving the render task promise. This PR reduces that delay to 0ms to evaluate whether tests run faster on CI.Note
Not intended for merge — purely a benchmark to compare CI run duration against the baseline.