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.
