Improve the polifill for setImmediate for max performance#72
Merged
arianrhodsandlot merged 2 commits intoarianrhodsandlot:mainfrom Dec 24, 2025
Merged
Improve the polifill for setImmediate for max performance#72arianrhodsandlot merged 2 commits intoarianrhodsandlot:mainfrom
arianrhodsandlot merged 2 commits intoarianrhodsandlot:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses a significant performance bottleneck in the previous setImmediate polyfill implementation, which relied on setTimeout(..., 0) as a fallback. While simple, this approach introduces delays (often clamped to at least 1-4ms in browsers due to timer nesting rules), limiting high-frame-rate scenarios.
On my machine, the old implementation capped performance at ~150 FPS (roughly 3x fast-forward ratio) in fast-forward mode.
The new polyfill uses a more efficient fallback (e.g., MessageChannel where available, with graceful degradation), allowing smoother execution and higher speeds (tested up to 4x+ fast-forward).