You can enable Parrot and run its related tests by passing `-PuseAntlr4=true` to gradle. Since the new parser is not mature enough in the past, we had to disable it by default to avoid some failed tests.
Currently Parrot can parse all groovy source codes of Apache Groovy and other famous groovy projects(e.g. Grails, Gradle, Spock, Geb) properly, so I am going to set aside some time to enable Parrot by default in the master branch.
发件人: 孙 岚 <firstname.lastname@example.org>
发送时间: 2017年4月21日 0:11
主题: About the performance between master and GROOVY_2_5_XHi all,
I noticed that the performance of master is better than GROOVY_2_5_X.
About 17% time saved when running tests in the TeamCity CI instance:
master costs 18m:55s(TeamCity CI, Parrot disabled)
viewLog.html?buildId=38801& tab=buildResultsDiv& buildTypeId=Groovy_Jdk8Build_2
GROOVY_2_5_X costs 22m:51s(TeamCity CI, without Parrot)
viewLog.html?buildId=38787& tab=buildResultsDiv& buildTypeId=Groovy_Jdk8Build_2
And about 37% time saved when running tests in the Travis CI instance:
master costs 20 min 25 sec(Travis CI, Parrot enabled)
GROOVY_2_5_X costs 32 min 52 sec(Travis CI, without Parrot)
Can we infer that the new parser Parrot does not impact the performance or even improve the performance somehow?