Multi Query 0.5 performance understanding

[Ramkumar KS]

Hi,

I have to check certain conditions and filter on around 10k vertices and planning to use multi query. 

As per the documentation given in http://s3.thinkaurelius.com/docs/titan/current/multiquery.html ,

TitanMultiVertexQuery mq = graph.multiQuery();

mq.direction(BOTH).labels("sibling");

for (Vertex f : v.getVertices(BOTH,"friend")) {

mq.addVertex((TitanVertex)f);

}

Map<TitanVertex,Iterable<TitanVertex>> results = mq.vertices();

As per the example above, since I am adding each vertex to the multi-query (text in bold and red), I have already downloaded the vertex . If I have to add 10K vertices to my muti query, that itself is going to take a considerable amount of time.

Is my understanding wrong or can any one help me understand how this is going to give performance improvement?

[Daniel Kuppitz]

It's a performance improvement for this particular query. Titan will issue a single query, rather than 10K queries. Getting the 10K input vertices as fast as possible is another problem / not related to the MultiQuery.

Cheers,

Daniel

--
You received this message because you are subscribed to the Google Groups "Aurelius" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aureliusgraph...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aureliusgraphs/472a947e-e2a5-4d05-9cd0-91756df21c15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.