Improve range() step costs
Graph API is nice, however in its current state it is unusable for large data sets due to high RU costs.
We are trying to implement paging for retrieving large amounts of data, however RU cost is unacceptable. Query "g.V().range(0,100)" costs 63.11 RU, however "g.V().range(2000,2100)" costs 338.06 RU even though it is same amount of data. Higher values are even more expensive meaning it's impossible to retrieve high amount of data without scaling up throughput.
Work for this feature has been started. Will update here when this feature becomes generally available.
Mark Williams commented
Glad this feature is being worked by the team. Thanks.
Any updates on this?
De Francesco, Pino commented
Ts the underlying capability has been completed, is there any ETA on this?
Some updates on this? It is not possible to use it, if the cost goes up exponentially.
Sorry to say..