You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/08/12 12:59:20 UTC

[jira] [Closed] (TINKERPOP-1228) Traversal Caching for TraversalOpProcessor

     [ https://issues.apache.org/jira/browse/TINKERPOP-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-1228.
---------------------------------------
    Resolution: Not A Problem
      Assignee: stephen mallette

This really isn't terribly useful an idea anymore with {{Bytecode}} representation of a {{Traversal}} and side-effect data cached on the server.

> Traversal Caching for TraversalOpProcessor
> ------------------------------------------
>
>                 Key: TINKERPOP-1228
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1228
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver, server
>    Affects Versions: 3.2.0-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>
> Serialized traversals are big which makes repeated requests for the same traversal expensive. Would be better to cache these somehow for re-use to avoid the serialization and network overhead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)