Repository navigation
Conversation
Median of 5 runs on the published packages (@fxts/core 2.0.1 vs p-map 7, Node 24): concurrentPool matches p-map exactly on uneven (455ms == 455ms) and uniform (511ms vs 510ms) I/O workloads, with the honest fine print that no-op tasks pay ~1us/item for order-preserving bookkeeping, and the concurrent column showing window behavior (654ms on uneven). The framing is deliberately "no performance trade", not "faster". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This branch has not been deployed
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.
Summary
Adds a "Measured" section to the p-limit/p-map migration guide (en/ko/ja/zh) with benchmark numbers taken against the published packages —
@fxts/core2.0.1 vsp-map7.0.7, Node 24, median of 5 runs per cell, result order/length asserted on every run:concurrentPoolconcurrentThe framing is deliberately "migrating is not a performance trade" rather than "faster": pool parity is exact on I/O-bound workloads, and the no-op row is kept as honest fine print (~1µs/item order-preserving bookkeeping that vanishes once tasks do real work). The
concurrentcolumn doubles as evidence for the guide's existing window-vs-pool warning.Test plan
vitepress build docspasses; prettier clean; all four locales updated identically🤖 Generated with Claude Code