[jira] [Commented] (GROOVY-11141) Improve documentation for indy performance system properties

["Daniel Sun (Jira)" <ji...@apache.org>]

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

Daniel Sun commented on GROOVY-11141:
-------------------------------------

{quote}
{{{}groovy.indy.callsite.cache.size{}}}, {{groovy.indy.optimize.threshold}} and {{{}groovy.indy.fallback.threshold{}}}. I've just set all setting to arbitrarily high values, and the performance is better
{quote}

{{groovy.indy.optimize.threshold}} and {{{}groovy.indy.fallback.threshold{}}} should be tuned and should not to be set to high values.


> Improve documentation for indy performance system properties
> ------------------------------------------------------------
>
>                 Key: GROOVY-11141
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11141
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Paul King
>            Priority: Major
>
> From slack:
> {quote}We have recently migrated from Groovy 3 to 4, and now have some performance issues, presumably because of the indy-only approach in Groovy 4. I have now identified some system properties, where the runtime behavior of the indy calls can be tweaked, namely {{groovy.indy.callsite.cache.size}}, {{groovy.indy.optimize.threshold}} and {{groovy.indy.fallback.threshold}}. I've just set all setting to arbitrarily high values, and the performance is better. But is there a more systematic approach, how to get "good" values? A documentation what those parameters influence, would be very much appreciated.
> {quote}



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