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

mgroovy commented on GROOVY-10307:
----------------------------------

[~emilles]:
* Just reran the test I have been using internally to judge Groovy performance 
(copyDominoDataEmailTest_Timed)
* All timings are in seconds, and each value represents just a single loop (so 
it is a very real world case from our code)
||Loop||Groovy 3.0.10||Groovy 4.0.1  ||Groovy 5.0.0 (SS 2022-05-07)||
|1|38.72219|41.799995|48.426486|
|2|4.998480|13.799789|17.556999|
|3|4.618735|13.302235|14.468128|
|4|4.677705|13.162331|12.906963|
|5|3.388114|12.517391|12.539367|
|6|4.133044|12.010279|11.813116|
|7|3.866016|11.529662|11.629216|
|8|5.497622|13.284200|13.481255|
|9|3.381661|10.910164|11.369198|
|10|3.323440|12.054754|11.307688|
* As one can see the Groovy 5.0.0 snapshot has in fact the same performance as 
Groovy 4.0.1, if the tests are executed directly one after another (with about 
10 min of project rebuild due to Groovy version change in between)
** (I was right to suss the results I reported earlier - I probably took the 
Groovy 4.0.1 measurements I looked up on my workstation, which evidently is a 
little bit slower than the notebook I am using right now...; sry for that)

> Groovy 4 runtime performance on average 2.4x slower than Groovy 3
> -----------------------------------------------------------------
>
>                 Key: GROOVY-10307
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10307
>             Project: Groovy
>          Issue Type: Bug
>          Components: bytecode
>    Affects Versions: 4.0.0-beta-1, 3.0.9
>         Environment: OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 
> (build 11.0.11+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode)
> WIN10 (tests) / REL 8 (web application)
> IntelliJ 2021.2 
>            Reporter: mgroovy
>            Priority: Major
>         Attachments: groovy_3_0_9_gc.png, groovy_3_0_9_loop2.png, 
> groovy_3_0_9_loop4.png, groovy_3_0_9_mem.png, groovy_4_0_0_b1_loop2.png, 
> groovy_4_0_0_b1_loop4.png, groovy_4_0_0_b1_loop4_gc.png, 
> groovy_4_0_0_b1_loop4_mem.png, 
> groovysql_performance_groovy4_2_xx_yy_zzzz.groovy, loops.groovy, 
> profile3.txt, profile4-loops.txt, profile4.txt, profile4d.txt
>
>
> Groovy 4.0.0-beta-1 runtime performance in our framework is on average 2 to 3 
> times slower compared to using Groovy 3.0.9 (regular i.e. non-INDY)
> * Our complete framework and application code is completely written in 
> Groovy, spread over multiple IntelliJ modules
> ** mixed @CompileDynamic/@TypeChecked and @CompileStatic
> ** No Java classes left in project, i.e. no cross compilation occurs
> * We build using IntelliJ 2021.2 Groovy build process, then run / deploy the 
> compiled class files
> ** We do _not_ use a Groovy based DSL, nor do we execute Groovy scripts 
> during execution
> * Performance degradation when using Groovy 4.0.0-beta-1 instead of Groovy 
> 3.0.9 (non-INDY):
> ** The performance of the largest of our web applications has dropped 3x 
> (startup) / 2x (table refresh) respectively
> *** Stack: Tomcat/Vaadin/Ebean plus framework generated SQL
> ** Our test suite runs about 2.4 times as long as before (120 min when using 
> G4, compared to about 50 min with G3)
> *** JUnit 5 
> *** test suite also contains no scripts / dynamic code execution
> *** Individual test performance varies: A small number of tests runs faster, 
> but the majority is slower, with some extreme cases taking nearly 10x as long 
> to finish
> * Using Groovy 3.0.9 INDY displays nearly identical performance degradation, 
> so it seems that the use of invoke dynamic is somehow at fault



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to