hasNext() slow for large number of incoming edges

Matthew Nguyen <nguyenm9@...>

Hey folks, I have a Vertex v who has about 7m+ incoming edges e.  The following query takes about 30+ seconds on a local installation of cassandra.




returns immediately with an answer.

Any idea why hasNext() would be so much slower?  I was under the impression that having "resultIterationBatchSize: 64" set would restrict to batching only any iteration to 64 elements at a time but it appears hasNext() is doing something else.  Is that correct?

Join janusgraph-users@lists.lfaidata.foundation to automatically receive all group messages.