anchor.diff:  where `x` is passed as a parameter from the client, there will be no additional compilation cost for future requests
   on that script.  Compilation of a script should be considered "expensive" and avoided when possible.
   
  +IMPORTANT: The parameterized script of `g.V(x)` is keyed in the cache differently than `g.V(y)` or even `g.V( x )`.
  +Scripts must be exact string matches for recompilation to be avoided.
  +
   [source,java]
   ----
   Cluster cluster = Cluster.open();
  
positive.code: 
  * Gremlin Server defaults to a very modest maximum heap size.  Consider increasing this value for non-trivial uses.
  Maximum heap size (`-Xmx`) is defined with the `JAVA_OPTIONS` setting in `gremlin-server.conf`.
  * When configuring the size of `threadPoolWorker` start with the default of `1` and increment by one as needed to a
  maximum of `2*number of cores`.
  * The "right" size of the `gremlinPool` setting is somewhat dependent on the type of scripts that will be processed
  
negative.code: 
  Gremlin Server provides for a single HTTP endpoint - a Gremlin evaluator - which allows the submission of a Gremlin
  script as a request.  For each request, it returns a response containing the serialized results of that script.
  To enable this endpoint, Gremlin Server needs to be configured with the `HttpChannelizer`, which replaces the default.
  The `WsAndHttpChannelizer` may also be configured to enable both WebSockets and the REST endpoint.
  `WebSocketChannelizer`, in the configuration file:
  
  [source,yaml]
  