Conversation
The emscripten main loop advanced the scheduler by a hardcoded 1/60s of guest time per browser frame, capping unthrottled speed at RAF_hz/60 and skewing paced emulation on displays faster than 60Hz. Mirror the native run loop instead: a paced machine steps guest time matching the real callback interval (clamped to [1/240, 1/15]s), and an unthrottled machine spends the whole callback emulating so speed is CPU-bound as on desktop. The unthrottled branch probes the wall clock every 128 slices rather than per slice: osd_ticks() crosses into JavaScript and timer-saturated guests run thousands of tiny timeslices per budget, where a per-slice probe rivalled emulation cost. assisted: GLM-5.3
Contributor
Author
vs
|
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
1 participant
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.
The emscripten main loop advanced the scheduler by a hardcoded 1/60s of guest time per browser frame, capping unthrottled speed at RAF_hz/60 and skewing paced emulation on displays faster than 60Hz. Mirror the native run loop instead: a paced machine steps guest time matching the real callback interval (clamped to [1/240, 1/15]s), and an unthrottled machine spends the whole callback emulating so speed is CPU-bound as on desktop. The unthrottled branch probes the wall clock every 128 slices rather than per slice: osd_ticks() crosses into JavaScript and timer-saturated guests run thousands of tiny timeslices per budget, where a per-slice probe rivalled emulation cost.
assisted: GLM-5.3