Skip to content

Add a simple benchmark script to bin/prism#3965

Merged
kddnewton merged 1 commit intomainfrom
bench
Mar 6, 2026
Merged

Add a simple benchmark script to bin/prism#3965
kddnewton merged 1 commit intomainfrom
bench

Conversation

@kddnewton
Copy link
Collaborator

No description provided.

@Earlopain
Copy link
Collaborator

Do we still need the older benchmark command? It's confusing to have two so similarly named.

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.

@kddnewton
Copy link
Collaborator Author

Yeah let's get rid of it.

@eregon
Copy link
Member

eregon commented Mar 6, 2026

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.

@kddnewton kddnewton merged commit 7414a8c into main Mar 6, 2026
67 checks passed
@kddnewton kddnewton deleted the bench branch March 6, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants