Conversation
Collaborator
|
Do we still need the older FWIW, I never used the benchmark command when looking at performance. It runs against so many variants which makes it cumbersome to use when actually wanting to compare/improve performance. |
Collaborator
Author
|
Yeah let's get rid of it. |
Member
|
It seems good to be able to compare to the other parsers though, and check whether the translation layers are faster than the original, but yeah if it's never used probably not much point to keep it here. For https://eregon.me/blog/2024/10/27/benchmarking-ruby-parsers.html I used something that was probably based on that script but a bit more complicated with more variants and getting more date. |
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.
No description provided.