[jira] [Commented] (GROOVY-8057) Terrible performance when enabling indy

["Daniel Sun (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GROOVY-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961145#comment-15961145 ] 

Daniel Sun commented on GROOVY-8057:
------------------------------------

Most of time-consuming tests are for parrot(https://scans.gradle.com/s/dllavnmfcl4si/tests), they are not compiled and executed. In other word, they are just parsed.
According to Jochen's hint, I found the possible cause of the performance issue is related to ASTComparatorCategory and AstDumper, becuase all of tests for parrot rely on ASTComparatorCategory and AstDumper, which are written in Groovy.

https://github.com/apache/groovy/blob/parrot/subprojects/groovy-parser-antlr4/src/test/groovy/org/apache/groovy/parser/antlr4/util/ASTComparatorCategory.groovy
https://github.com/apache/groovy/blob/parrot/subprojects/groovy-parser-antlr4/src/test/groovy/org/apache/groovy/parser/antlr4/util/AstDumper.groovy



> Terrible performance when enabling indy
> ---------------------------------------
>
>                 Key: GROOVY-8057
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8057
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 3.0
>         Environment: Java 8, TeamCity instance(http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_Antlr4grammar)
>            Reporter: Daniel Sun
>            Priority: Critical
>
> When enabling indy by default, running test cases cost much more time than before(http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_Antlr4grammar).
> Indy(costs  	1h:37m):
> http://ci.groovy-lang.org/viewLog.html?buildId=37256&tab=buildResultsDiv&buildTypeId=Groovy_Antlr4grammar
> no Indy(costs 	21m:59s):
> http://ci.groovy-lang.org/viewLog.html?buildId=37254&tab=buildResultsDiv&buildTypeId=Groovy_Antlr4grammar



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)