the low hanging fruit is the time needed to create a PP parser (time for
I profiled PPSmalltalkParser over a bench used by Lucas Renggli a few
years ago, and PPSmalltalkParser spends half the time in "new" (and it
is a lot slower than it used to be).
Le 21/02/2015 21:13, Tudor Girba a écrit :
On Sat, Feb 21, 2015 at 8:07 PM, Thierry Goubier
<thierry.goubier(a)gmail.com <mailto:firstname.lastname@example.org>> wrote:
Le 21/02/2015 11:14, Jan Kurš a écrit :
I was not aware about some exponential element in the overall
complexity, it is strange and I will investigate it. Thank you
for pointing this out.
In general, it is hard to add features into the PetitParser and
performance. Therefore, we work on a tool, that will take
analyze it and generates faster parser. The idea is to use
while developing the grammar and than generate a fast parser for
use. We hope we will be present the tool during the next ESUG.
I certainly be interested with what you come up with. From profiling
PetitParser, it seems there is at least one low-hanging fruit in
term of performance.
What is that log hanging fruit?