- hasNext() slow for large number of incoming edges
Re: hasNext() slow for large number of incoming edges
toggle quoted messageShow quoted text
I don't know what it does underneath.
But if you want to just check about edge existence with hasNext, Can you try with limit 1.
On Tue, 25 Jan 2022, 23:05 Matthew Nguyen via lists.lfaidata.foundation, <nguyenm9=aol.com@...> wrote:
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 firstname.lastname@example.org to automatically receive all group messages.