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
Add an HTTP parser to parser_benchmarks #210
Comments
Nice work with the benchmark and thank you for taking the time to do this. 😄 Everything looks good. You might also want to compare pest against the master branch since there are some performance improvements coming up in the next version. Regarding the HTTP benchmark, this would have a lower priority for now. We're currently working a lot on improving the developer experience and the docs which is quite harder than I first thought. EDIT: I've checked the other benchmarks. Congrats on the performance gains! |
plus tests, benchmark and a fuzzing target based on pest-parser#372 by @adamAndMath Closes pest-parser#210 Co-authored-by: Adam <adam.and.math@gmail.com>
plus tests, benchmark and a fuzzing target based on pest-parser#372 by @adamAndMath Closes pest-parser#210 Co-authored-by: Adam <adam.and.math@gmail.com>
plus tests, benchmark and a fuzzing target based on #372 by @adamAndMath Closes #210 Co-authored-by: Adam <adam.and.math@gmail.com> Co-authored-by: Tomas Tauber <me@tomtau.be> Co-authored-by: Adam <adam.and.math@gmail.com>
Hello!
I spent some time cleaning up the old nom_benchmarks repository in a more general parser_benchmarks. Since we're reaching the point where the various parser libraries reach the same performance, it's getting interesting to have a good way to compare them on the same tests, and transfer techniques from one to the next.
I have added your JSON example and put it to work on the other example files (and added the
canada.json
file you use for your benchmarks): https://github.com/Geal/parser_benchmarks/tree/master/jsonInterestingly, I have not been able to make the nom parser faster than the pest one for that file :)
Could you check the benchmark to see if I have not missed anything in how to use pest?
Also, do you think you could contribute a HTTP parser to the repository?
The text was updated successfully, but these errors were encountered: