Skip to content

test(napi): add NAPI parser benchmark#9045

Merged
graphite-app[bot] merged 1 commit intomainfrom
02-11-test_napi_add_napi_parser_benchmark
Feb 11, 2025
Merged

test(napi): add NAPI parser benchmark#9045
graphite-app[bot] merged 1 commit intomainfrom
02-11-test_napi_add_napi_parser_benchmark

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented Feb 11, 2025

Add a quick benchmark for NAPI parser. It's included in our CI benchmarks, because likely will produce too much variance, but it's useful for local runs.

@github-actions github-actions bot added the C-test Category - Testing. Code is missing test cases, or a PR is adding them label Feb 11, 2025
Copy link
Member Author

overlookmotel commented Feb 11, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@overlookmotel overlookmotel marked this pull request as ready for review February 11, 2025 13:58
@overlookmotel overlookmotel changed the base branch from 02-11-fix_ast_estree_fix_serializing_regexpliteral_ to graphite-base/9045 February 11, 2025 14:04
@overlookmotel
Copy link
Member Author

Can't see any downside to adding this, so merging without review.

@overlookmotel overlookmotel added the 0-merge Merge with Graphite Merge Queue label Feb 11, 2025
Copy link
Member Author

overlookmotel commented Feb 11, 2025

Merge activity

  • Feb 11, 9:06 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Feb 11, 9:06 AM EST: A user added this pull request to the Graphite merge queue.
  • Feb 11, 9:15 AM EST: A user merged this pull request with the Graphite merge queue.

@graphite-app graphite-app bot changed the base branch from graphite-base/9045 to main February 11, 2025 14:09
Add a quick benchmark for NAPI parser. It's included in our CI benchmarks, because likely will produce too much variance, but it's useful for local runs.
@github-actions github-actions bot added the A-ast Area - AST label Feb 11, 2025
@graphite-app graphite-app bot force-pushed the 02-11-test_napi_add_napi_parser_benchmark branch from 165d78b to ef553b9 Compare February 11, 2025 14:09
@graphite-app graphite-app bot merged commit ef553b9 into main Feb 11, 2025
19 checks passed
@graphite-app graphite-app bot deleted the 02-11-test_napi_add_napi_parser_benchmark branch February 11, 2025 14:15
graphite-app bot pushed a commit that referenced this pull request Feb 11, 2025
…s on JS side (#9044)

Add a "reviver" function to `JSON.parse` in NAPI parser module, to correctly set `value` field of `Literal`s for `RegExp`s and `BigInt`s.

Surprisingly, judging by a local run of NAPI parser benchmarks (added in #9045), this does not seem to hurt performance. In fact the benchmarks were showing a ~2% speed-up. That's clearly nonsense - just noise - but it does suggest at least that this isn't hurting performance significantly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0-merge Merge with Graphite Merge Queue A-ast Area - AST C-test Category - Testing. Code is missing test cases, or a PR is adding them

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant