@amon: A very nice summary. Thanks!
@mdorman: At this point many people have more & more recent experience with
Marpa::R2 applications than I do. [ Though I still know the internals
better than anyone, I guess. :-) ] amon is an expert, and also the author
of some very good tutorials.
On Tue,
A high cost in stack_step is not entirely unsurprising, but if it is taking
too long subjectively then there are some points that might be fixable.
Note that stack_step() implements the semantics of your parser, which are
only run *after* a successful parse. I don't think using events in the
:* Monday, November 20, 2017 5:09 PM
> *To:* Marpa Parser Mailing LIst <marpa-parser@googlegroups.com>
> *Subject:* Re: Are there good strategies for diagnosing performance
> issues?
>
>
>
> I'm very rusty at looking at profiles of Marpa::R2, but I hope some
> off-the-t
I'm very rusty at looking at profiles of Marpa::R2, but I hope some
off-the-top-of-my-head remarks might be useful. Typically, almost all the
time of an R2 parse is taken up by the Perl layer, and by the semantics --
the parse itself is almost free. So looking at how you handle the
semantics may
