You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by sp...@apache.org on 2015/08/20 22:15:45 UTC
[5/8] incubator-tinkerpop git commit: Fixed typo in Gremlin Server
cache management docs.
Fixed typo in Gremlin Server cache management docs.
Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/ee6b17ef
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/ee6b17ef
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/ee6b17ef
Branch: refs/heads/master
Commit: ee6b17ef39405561ee080ddfa32579c53e233c02
Parents: 1903d25
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Thu Aug 20 15:46:17 2015 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Thu Aug 20 15:46:17 2015 -0400
----------------------------------------------------------------------
docs/src/gremlin-applications.asciidoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/ee6b17ef/docs/src/gremlin-applications.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/gremlin-applications.asciidoc b/docs/src/gremlin-applications.asciidoc
index 2949957..c82e68b 100644
--- a/docs/src/gremlin-applications.asciidoc
+++ b/docs/src/gremlin-applications.asciidoc
@@ -775,16 +775,16 @@ image:gremlin-parameterized.png[width=150,float=left] Use script parameterizatio
Cache Management
^^^^^^^^^^^^^^^^
-If Gremlin Server processes a large number of unique scripts, the cache will grow beyond the memory available to Gremlin Server and an `OutOfMemoryException` will loom. Script parameterization goes a long way to solving this problem and running out of memory should not be an issue for those cases. If it is a problem or if there is no script parameterization due to a given use case (perhaps using with use of <<sessions,sessions>>), it is possible to better control the nature of the script cache from the client side, by issuing scripts with a parameter to help define how the garbage collector should treat the references.
+If Gremlin Server processes a large number of unique scripts, the cache will grow beyond the memory available to Gremlin Server and an `OutOfMemoryError` will loom. Script parameterization goes a long way to solving this problem and running out of memory should not be an issue for those cases. If it is a problem or if there is no script parameterization due to a given use case (perhaps using with use of <<sessions,sessions>>), it is possible to better control the nature of the script cache from the client side, by issuing scripts with a parameter to help define how the garbage collector should treat the references.
The parameter is called `#jsr223.groovy.engine.keep.globals` and has four options:
* `hard` - available in the cache for the life of the JVM (default when not specified).
-* `soft` - retained until memory is "low" and should be reclaimed before an `OutOfMemoryException` is thrown.
+* `soft` - retained until memory is "low" and should be reclaimed before an `OutOfMemoryError` is thrown.
* `weak` - garbage collected even when memory is abundant.
* `phantom` - removed immediately after being evaluated by the `ScriptEngine`.
-By specifying an option other than `hard`, an `OutOfMemoryException` in Gremlin Server should be avoided.
+By specifying an option other than `hard`, an `OutOfMemoryError` in Gremlin Server should be avoided. Of course, this approach will come with the downside that compiled scripts could be garbage collected and thus removed from the cache, forcing Gremlin Server to recompile later.
[[sessions]]
Considering Sessions