[
https://issues.apache.org/jira/browse/GROOVY-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690659#comment-17690659
]
Ken Hu commented on GROOVY-10934:
---------------------------------
Thanks for taking the time to look into this [~emilles]
I'm still in the process of trying to create a simple example script that only
uses Java/Groovy classes that demonstrate this behavior. I'll take some
measurements after I get the example up and running. The product where I'm
seeing this issue is the Gremlin Console (which uses groovysh) so this is
actually related to GROOVY-9785. There is a good chance we will be able to
solve both of these issues at once.
> 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)
