Hi Ashish,
OTLP is serial and OLAP is parallel. What would be smart is if we had an
interface liked "ThreadSafeStep" which meant that a particular step was thread
safe. Then for a chain of "thread safe" steps, we could thread that section.
For things like ReducingBarrierSteps, etc., (not thread safe) it would go back
to single threaded. Finally, we could then have a
ParallelTraversalOptimizationStrategy that would introspect and do the
appropriate threading infrastructure at compile time. Perhaps you could make a
ticket detailing your use case and requirements and we can work towards getting
that into 3.2.0.
https://issues.apache.org/jira/browse/TINKERPOP3
Thanks,
Marko.
http://markorodriguez.com
On Nov 23, 2015, at 4:41 PM, Ashish Nagavaram <[email protected]>
wrote:
> hi,
> The default traversal code , traverses the graph sequentially after
> contracting the traversal plan. Is there a parallel version available? I
> understand that this will have a impact on throughput of the machine, but for
> latency critical applications throughput vs latency might be ok. We can maybe
> initialize the traversal with a ParallelTraversal (similar to default
> traversal api).
> Currently for my use-case, I create a future task for each fork and then run
> a intersection across results .. which might not always work.
