jglapa commented on issue #15293: URL: https://github.com/apache/grails-core/issues/15293#issuecomment-3659335203
@jdaugherty Amazing! I wasn't aware that indy could still be disabled with Groovy 4. I can confirm that in both my benchmark and the application, performance is back on par with Grails 6/Groovy 3, allowing us to continue with the upgrade. ## Benchmark Results | Test Type | Grails 6 | Grails 7 (indy) | Grails 7 (no indy) | |-----------|-----------|-----------------|--------------------| | bootWar | 61.18 ms | 323.48 ms | 64.24 ms | | bootRun | 103.96 ms | 858.00 ms | 115.12 ms | ## Additional Notes **PS:** I tried the indy version with Java 21, and that didn't show any difference. I would be skeptical that JVM upgrades will address such a significant performance gap. **PS2:** Is the Grails team in touch with the Groovy maintainers? Are they aware of this issue? It's unclear who would choose the indy version at the moment or in the future.. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
