You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optimizes the common queue.add(fn) path when no options are passed.
This avoids the default {} parameter, object spread, repeated option reads, and per-task noop cleanup closure for the no-options path while preserving behavior for timeout, priority, abort, and explicit options.
Thanks, but I don’t think this is the right tradeoff.
The current implementation has a simple invariant: normalize options once, then use that normalized object throughout add(). This PR makes the central lifecycle path harder to audit by adding a special no-options branch and separate captured values for id, signal, timeout, and priority.
The benchmark is also an isolated enqueue-only case on a paused queue. That makes option normalization overhead look more important than it likely is in real p-queue usage, where the queued async work, timers, abort handling, and scheduling behavior dominate.
Thanks, but I don’t think this is the right tradeoff.
The current implementation has a simple invariant: normalize options once, then use that normalized object throughout add(). This PR makes the central lifecycle path harder to audit by adding a special no-options branch and separate captured values for id, signal, timeout, and priority.
The benchmark is also an isolated enqueue-only case on a paused queue. That makes option normalization overhead look more important than it likely is in real p-queue usage, where the queued async work, timers, abort handling, and scheduling behavior dominate.
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
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.
Summary
Optimizes the common
queue.add(fn)path when no options are passed.This avoids the default
{}parameter, object spread, repeated option reads, and per-task noop cleanup closure for the no-options path while preserving behavior for timeout, priority, abort, and explicit options.Benchmarks
Node.js v20.19.5
add-no-options-pausedValidation
Existing behavior tests cover no-options
.add(), options copying, priority, timeout, abort signals, listener cleanup, andrunningTasks.