What constitutes good runtime parser performance? #3413
Unanswered
michaelfortunato
asked this question in
Q&A
Replies: 1 comment 1 reply
-
it's not exactly easy to predict what makes some parsers faster than others (e.g. machine specs/good cpu caching can play a huge role sometimes), but there are a few numbers you can eye to ensure parser performance does not degrade a lot
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have written a tree-sitter grammar which generates a parser than takes ~80ms to parse my language's 6000 line file.
Using the files attached here, nvim-treesitter/nvim-treesitter-context#220, it took my machine 120ms to parse combined-20k.py, so python's performance is better than my parser from this one off, but they are comparable.
Are these the parse times I should when parsing general programming languages of these file sizes? Is there any CI/CD code on the major repos that track parser runtime performance?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions