You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Kyle Moore (Jira)" <ji...@apache.org> on 2022/07/28 00:08:00 UTC

[jira] [Created] (GROOVY-10709) Performance regression in Gradle with Groovy 4

Kyle Moore created GROOVY-10709:
-----------------------------------

             Summary: Performance regression in Gradle with Groovy 4
                 Key: GROOVY-10709
                 URL: https://issues.apache.org/jira/browse/GROOVY-10709
             Project: Groovy
          Issue Type: Bug
    Affects Versions: 4.0.3
            Reporter: Kyle Moore
         Attachments: test-results-largeAndroidBuildPerformanceAdHocTest.zip

The Gradle team is exploring Groovy 4 as the included version for our next major release.

Our initial performance tests show a significant regression which may be caused by excessive method calls to generate stack traces.

I will attach a tome of performance data comparing Gradle built with Groovy 3.0.11 vs. 4.0.3. Interesting measurements are available at:
* run-help/7.6-20220727093039+0000/diffs/run-help-7.6-20220727093039+0000-vs-7.5-cpu-simplified-backward-diff-flames.svg
* performance-tests/report/index.html -> comparing "Gradle 7.5" vs. "Current Gradle" shows a significant regression.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)