Generating stubs with antlr2 parser is much faster than parsing with antlr2
parser, if we can work out the cause, the performance issue of generating
stubs with antlr4 can be solved. Assuming some operations are skipped.
Here is the labs branch:
https://github.com/apache/groovy/tree/nextflow-perf-
Hi Paolo,
When stubs are being generated, the first stubs generation will probably
miss cache, but the performance of Parrot parser relies on its cache
heavily, so it will run faster and faster while cache is filled fuller and
fuller, which is the reason why antlr4 recommends NEVER clear its cache
Hi Daniel,
Thanks for looking at this. I've reported the problem in the IntelliJ issue
tracking. Let me know if I can help further.
https://youtrack.jetbrains.com/issue/IDEA-230943
Cheers,
Paolo
On Sun, Jan 19, 2020 at 12:15 PM Daniel.Sun wrote:
> Hi Paolo,
>
> When stubs are being generate
Hi Paolo,
I'm thinking about how to solve the performance issue:
1) Improve the performance of Parrot parser even if the groovy code is
parsed for the first time
2) Generate stubs in parallel
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twit
This sounds great!
On Sun, Jan 19, 2020 at 7:48 PM Daniel.Sun wrote:
> Hi Paolo,
>
> I'm thinking about how to solve the performance issue:
>
> 1) Improve the performance of Parrot parser even if the groovy code is
> parsed for the first time
> 2) Generate stubs in parallel
>
> Cheers,
> Da
