-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process: improve queueMicrotask performance #28093
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
'use strict'; | ||
|
||
const { FunctionPrototype } = primordials; | ||
const FunctionPrototypeBind = FunctionPrototype.bind; | ||
|
||
const { | ||
// For easy access to the nextTick state in the C++ land, | ||
|
@@ -136,15 +137,13 @@ function nextTick(callback) { | |
} | ||
|
||
let AsyncResource; | ||
const defaultMicrotaskResourceOpts = { requireManualDestroy: true }; | ||
function createMicrotaskResource() { | ||
// Lazy load the async_hooks module | ||
if (!AsyncResource) { | ||
if (AsyncResource === undefined) { | ||
AsyncResource = require('async_hooks').AsyncResource; | ||
} | ||
return new AsyncResource('Microtask', { | ||
triggerAsyncId: getDefaultTriggerAsyncId(), | ||
requireManualDestroy: true, | ||
}); | ||
return new AsyncResource('Microtask', defaultMicrotaskResourceOpts); | ||
} | ||
|
||
function runMicrotask() { | ||
|
@@ -172,7 +171,7 @@ function queueMicrotask(callback) { | |
const asyncResource = createMicrotaskResource(); | ||
asyncResource.callback = callback; | ||
|
||
enqueueMicrotask(FunctionPrototype.bind(runMicrotask, asyncResource)); | ||
enqueueMicrotask(FunctionPrototypeBind(runMicrotask, asyncResource)); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same question here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure. @mcollina flagged this for me and I've noticed it's definitely slower. He might have more insights — not sure if he talked to the V8 team about it at all. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is an ongoing effort to optimize frozen object performance, see https://bugs.chromium.org/p/v8/issues/detail?id=6831 and https://bugs.chromium.org/p/v8/issues/detail?id=8538 we may revisit this when the patches upstream land here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
We are. Essentially accessing them is slower than accessing normal objects. We should look on not reading properties in hot code path, but maybe only once when the module is loaded. |
||
} | ||
|
||
module.exports = { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is moving this safe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. This is only needed for the case where
requireManualDestroy = false
. We pass it on directly to C++ inregisterDestroyHook
.