experiment with moving eventLoopTick
to rust
#998
Draft
+149
−57
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.
moves promise resolution and tracking from js to rust, curious to see if we could gain any perf from moving
eventLoopTick
to rust.right now we have the rust event loop calling into JS to actually dispatch most of the event loop (which also often involves calling op_run_microtasks from JS, which calls back into rust!)
we might be able to skip a hop and eliminate
op_run_microtasks
entirelyso far the perf impact on the promise resolution is roughly neutral (as expected). it might take moving the whole thing to rust to see a real impact (if any)
bench: