You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2016/06/23 23:03:16 UTC

[jira] [Commented] (GROOVY-7873) Regression performance issue in string methods

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

Paul King commented on GROOVY-7873:
-----------------------------------

There was a performance increase in other scenarios. Obviously our scenario coverage wasn't good enough. We'll possibly have to revert if we can't find something that improves your case too.

> Regression performance issue in string methods
> ----------------------------------------------
>
>                 Key: GROOVY-7873
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7873
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.4.7
>            Reporter: Tadas Krivickas
>            Priority: Critical
>         Attachments: test.groovy
>
>
> Starting with 2.4.7, performance in string processing (in certain scenarios) has decreased dramatically. Specifically, it happens when using {{stripMargin()}} on a {{GString}} that has a variable substitution with a huge String value. In our app performance decrease was from tens of miliseconds to 1+ minute. 
> I suspect the latest refactoring in string methods.
> Attaching a test case.
> {code}
> R2D2:groovystrperf tadaskay$ /usr/local/Cellar/groovy/2.4.7/bin/groovy test.groovy
> Took 1456 ms
> R2D2:groovystrperf tadaskay$ /usr/local/Cellar/groovy/2.4.5/bin/groovy test.groovy
> Took 43 ms
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)