At the moment if you run a query like g.V('1').outE(), for every edge on the vertex '1' GafferPop will run a GetElements operation with only one seed. This can be very problematic for queries that touch a lot of data as each operation has overhead and gets logged so could end up with thousands of operations being called at once.
To fix this we might need to implement custom vertex/edge traversal strategies so that all the seeds are acquired first then added to one big operation rather than lots of smaller ones.
At the moment if you run a query like g.V('1').outE(), for every edge on the vertex '1' GafferPop will run a GetElements operation with only one seed. This can be very problematic for queries that touch a lot of data as each operation has overhead and gets logged so could end up with thousands of operations being called at once.
To fix this we might need to implement custom vertex/edge traversal strategies so that all the seeds are acquired first then added to one big operation rather than lots of smaller ones.