Add initial benchmark for parser#4928
Open
shreyadesai20042009 wants to merge 1 commit intoboa-dev:mainfrom
Open
Add initial benchmark for parser#4928shreyadesai20042009 wants to merge 1 commit intoboa-dev:mainfrom
shreyadesai20042009 wants to merge 1 commit intoboa-dev:mainfrom
Conversation
Test262 conformance changes
Tested main commit: |
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
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
This PR adds an initial benchmark for parser execution using criterion in the benches directory.
🎯 Purpose
The benchmark helps measure the performance of parsing and executing JavaScript code in Boa.
It provides a baseline for future performance improvements and optimizations.
📊 What It Does
Adds a new benchmark file in benches/
Uses criterion for performance measurement
Runs a sample JavaScript workload
Generates performance reports under target/criterion
🚀 How To Run
To run benchmarks:
cargo bench
🔍 Why This Is Useful
Provides a baseline for performance comparison
Helps detect regressions
Supports future optimization work
Improves observability of parser/runtime performance
This benchmark can be extended in future PRs to: