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

["Jochen Theodorou (Jira)" <ji...@apache.org>]

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

Jochen Theodorou commented on GROOVY-10709:
-------------------------------------------

I have a bit trouble reading this versus flame graph. But yes, there is a difference in that ClosureMetaClass.invokeOnDelegationObjects now produces stack traces, where it did no do that in the past. First I was thinking about  GROOVY-7232. But after writing a lengthy comment here for like an hour I am not sure. At the very least it is not the change in the default strategy I think.

Why is there code, that tries to find a  lookup method and then fails to do so?




> 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
>            Priority: Major
>         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 specialized exceptions that don't have stacks.
> 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)