[
https://issues.apache.org/jira/browse/GROOVY-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578452#comment-17578452
]
Paul King commented on GROOVY-10709:
------------------------------------
I re-ran my benchmark for the latest 4.0.5-SNAPSHOT. Here are the results:
{noformat}
Benchmark Mode Cnt Score Error Units
Main.testCallGroovy3Classic avgt 200 0.320 ± 0.001 ms/op
Main.testCallGroovy3Indy avgt 200 0.316 ± 0.001 ms/op
Main.testCallGroovy4 avgt 200 0.649 ± 0.003 ms/op
Main.testCallJavaImplementingGroovyObject avgt 200 0.282 ± 0.001 ms/op
{noformat}
> 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
> Assignee: Paul King
> Priority: Major
> Fix For: 4.0.5
>
> 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)
