Comparison diagram isn't very informative and makes pest look bad.

[pest-parser]

Comparison diagram isn't very informative and makes pest look bad.

[lwandrebeck]

There's a nom_benchmark repository in geal/gcouprie (nom's author) github that could be used (it runs nom, pest and one or two others as far as i can remember), but it's quite outdated, and needs some work.
Otherwise, maybe we should have our own benchmark suite to keep a good tracking of pest perfs throughout time ? I'll be glad to give a hand on that front.

[dragostis]

Thanks for the raising this issue. Here's my stance on the matter: both parsers listed in the comparison offer great performance and pest's goal is not to compete with them, but merely to show how pest can offer performance in the same order of magnitude.

Now, things will be different in 3.0. I have rewritten the generator and I'm working on the optimizer with great results.

[LeoDog896]

I can't find any new benchmarks on pest - is there any updated information from the performance benchmarks mentioned above?

[LeoDog896]

Good idea! It'll be nice if we can get an official repo created for that.

[lwandrebeck]

There's a nom_benchmark repository in geal/gcouprie (nom's author) that could be used (it runs nom, pest and one or two others as far as i can remember), but it's quite outdated, and needs some work.
Otherwise, maybe we should have our own benchmark suite to keep a good tracking of pest perfs throughout time ? I'll be glad to give a hand on that front.
Edit : https://github.com/rust-bakery/parser_benchmarks for reference

[tomtau]

One more repo that's more up to date: https://github.com/rosetta-rs/parse-rosetta-rs#results