-
Notifications
You must be signed in to change notification settings - Fork 170
Basic benchmark #684
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
base: main
Are you sure you want to change the base?
Basic benchmark #684
Conversation
Thanks. I'll try to play with this soon. |
Beyond that, I don't have time right now to review more. @namannimmo10 if you have time to test this out, that would be great. |
@certik @namannimmo10 i think it's ready for trying and reviewing, you could try it on your machines. |
Any news on this? |
This needs rebasing on top of the latest master and we have to review and test this. My apologies that we didn't get to it yet. |
@Thirumalai-Shaktivel Since this is related to parsers, would you mind completing this and getting this in. See above comment for what needs to be done to get this in. |
In general benchmarking the parser is a lower priority, so if it is too much work, let's work on that later. If it is easy to wrap this PR up in a clean way, then we can finish it. |
Basic benchmark for parser, it will work as same as testing.
i will continue it, and puts some examples here for reviewing.