You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing a GraphQL query which has a large result-set, it might be efficient to use pagination. One can do this by using a combination of limit and offset. This works fine for smaller offsets, but as it increase, response time also seems to increase. So my guess would be, that the full query result is generated, and only the offset - limit part is being returned. But as process time increase, really large offsets take forever to finish, while the number of results might be the same as offset 0.
Is there any way to improve this?
Or if not, is there any other way to accomplish the same thing?
Ask a question
When doing a GraphQL query which has a large result-set, it might be efficient to use pagination. One can do this by using a combination of
limit
andoffset
. This works fine for smaller offsets, but as it increase, response time also seems to increase. So my guess would be, that the full query result is generated, and only the offset - limit part is being returned. But as process time increase, really large offsets take forever to finish, while the number of results might be the same as offset 0.Is there any way to improve this?
Or if not, is there any other way to accomplish the same thing?
The query used:
With variables:
The text was updated successfully, but these errors were encountered: