You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2023/02/15 14:50:00 UTC

[jira] [Commented] (GROOVY-10934) Performance when Resolving Import Statement

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

Eric Milles commented on GROOVY-10934:
--------------------------------------

Can you provide a simple example script?  Do you have timing for a release when it was considered "good" and timing from the first release where performance degraded enough to be noticeable?

> Performance when Resolving Import Statement
> -------------------------------------------
>
>                 Key: GROOVY-10934
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10934
>             Project: Groovy
>          Issue Type: Question
>          Components: Groovysh
>    Affects Versions: 3.0.5, 2.5.17
>            Reporter: Ken Hu
>            Priority: Major
>
> The time it takes to resolve imports for scripts seems to have increased substantially since fixing the issue for GROOVY-5103. This can have a major impact on performance when a simple script that contains many imports is executed because the majority of the time will be spent resolving the imports. Are there any workarounds for this?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)