Add in-repo benchmark suite with CPU/RAM monitoring - #34
Open
adarshmadrecha wants to merge 1 commit into
Open
Conversation
Introduce npm run bench to measure pack/unpack throughput, latency percentiles, process CPU usage, heap/RSS, and event-loop delay across synthetic GeoJSON, e-commerce, API, nested, and mixed datasets. Include a captured BASELINE.md from this machine for comparison.
3 tasks
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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
benchmark/bench.jsandbenchmark/datasets.jswith synthetic real-world-like datasets.npm run bench,npm run bench:md,npm run bench:json.benchmark/BASELINE.mdsample results (Node v25, win32 x64).Test plan
npm testpassesnpm run benchruns and prints CPU/RAM metricsnpm run bench:mdproduces markdown tableNotes
No library API or packed-format changes — benchmark-only.