-
-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to define lark grammar for best parsing performance #1404
Comments
The first recommendation is always to try and use Try to have as much as possible in your grammar be a terminals, not rules, however you shouldn't use non-regular regex features like lookaheads/behinds. If you have to use earley because your grammar is ambiguous for some reason or just doesn't fit into LALR, you should make sure that your regex patterns are as simple and non-overlapping as possible, and make sure that your grammar is left-recurisve, i.e. a rule only (or at least primarily) appears as it's own first child. You can try switching to You can also switch to use PyPy instead of CPython for a very huge boost almost always. |
Oh, also use a newer version of |
Try to let the regex engine capture as much as possible. For example, this is VERY bad: bare_id : (letter| underscore) (letter|digit|underscore|id_chars)* Try making bare_id (and its dependencies) into a terminal. It should help a lot. Avoid unnecessary right-recursion. This is very bad: semi_affine_expr : "(" semi_affine_expr ")" -> semi_affine_parens
| semi_affine_expr "+" semi_affine_expr -> semi_affine_add See the calculator example. Also, try reducing the number of rules. You have a lot of unnecessary duplication of rules. It's not worth it to use Earley to validate every corner of the input. Just make sure it parses into the correct structure, and validate afterwards. |
@erezsh, I have question on the difference between rules vs terminal. Is there any difference in the way a rule and a terminal is processed internally by lark. specifically with respect to your suggestion on keeping regrex's to terminals? |
Yes, there's an important difference. A terminal turns into a single regular expression. So in the following: X: "a" "b" "c"
x: "a" "b" "c"
|
https://lark-parser.readthedocs.io/en/stable/grammar.html# Hi @erezsh, the document above is where I started to understand about lark grammar definition. Is there any other documents that describe how to define grammar using lark? Specifically guidelines on the best practices for grammar definition. |
I think we have good information to move forward here. So, closing the issue for now. |
What is your question?
I am currently using pymlir for a project. pymlir is an open source project that allows to parse mlir grammar using lark. I currently have mlir files of ~2k lines and parsing this takes multiple minutes. I am looking at ways to optimize the parsing time and my target is to bring this below a minute. Are there any best practices defined in grammar definition so that lark can optimally parse a DSL.
If you're having trouble with your code or grammar
Provide a small script that encapsulates your issue.
Explain what you're trying to do, and what is obstructing your progress.
The text was updated successfully, but these errors were encountered: