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

ASF GitHub Bot commented on TINKERPOP-2138:
-------------------------------------------

spmallette commented on pull request #1046: TINKERPOP-2138 Provide way to 
disable the global function cache
URL: https://github.com/apache/tinkerpop/pull/1046
 
 
   https://issues.apache.org/jira/browse/TINKERPOP-2138
   
   Added a new `globalFunctionCacheEnabled` configuration to the 
`GroovyCompilerGremlinPlugin` and an overriding setting for sessions on 
`SessionOpProcessor` that disables the global function cache.  In cases where 
you don't need the cache (i.e. don't use global functions) it does remove a bit 
of reflection based processing from every single script request and obviously 
saves on memory formerly used by the cache. 
   
   All tests pass with `docker/build.sh -t -n -i`
   
   VOTE +1
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Provide a configuration to disable the global closure cache
> -----------------------------------------------------------
>
>                 Key: TINKERPOP-2138
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2138
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: groovy
>    Affects Versions: 3.3.5
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>
> There are situations where users and/or providers might want to disable the 
> global closure cache in the {{GremlinGroovyScriptEngine}} - provide a 
> {{Customizer}} to do that (or modify an existing one if possible to carry the 
> configuration option). By default, the cache would remain enabled for now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to