-
Notifications
You must be signed in to change notification settings - Fork 48
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
Slow parse times #18
Comments
Are you on aim? I've done a lot research regarding this and it's easier to explain there. Sent from my iPhone On Feb 4, 2012, at 3:15 PM, James Idereply@reply.github.com wrote:
|
Sure, my SN is chocoflyer. |
I'm curious what the latest is here. I am interesting in faster parses. Even a little pointer in the right direction might help with optimization. |
I have tried Ruby PEG parser generator |
I haven't done any profiling so this is a rather generic issue, but the parser performance is rather slow. For example:
I'm surprised because the theoretical performance should be quite high so I'm guessing that high number of object allocations, especially for the deep expression productions (how many nodes does it take to represent a simple string literal?) is hurting performance.
The text was updated successfully, but these errors were encountered: