[GROOVY-10709] Performance regression in Gradle with Groovy 4

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.3
• Fix Version/s: 4.0.5
• Assignee: Paul King
• Reporter: Kyle Moore
• Created: 28/Jul/22 00:07
• Updated: 12/Feb/23 15:51
• Resolved: 07/Aug/22 14:19

Description

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.

Issue Links

• is related to: GROOVY-10290 Dynamic Groovy code in Gradle doesn't compile because of $getLookup() method is not static
• is related to: GROOVY-10450 Cannot call BiPredicate methods on closures or lambdas on JRE 16+
• is related to: GROOVY-10273 New $getLookup() method is not marked as generated or internal
• relates to: GROOVY-10931 Remove $getLookup method generation (Groovy 4+)
• links to: GitHub Pull Request #1757