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
One of the cons of using cursors is that it doesn't let you skip pages. In other words, if you want to get page 100, you need to get page 1, 2,3,4 ..., 99.
It's common that Apps get the count of a set and execute multiple requests in parallel to get all the pages. For instance, if I want to iterate over all products, I will execute a count query products/count.json, grab that number (e.g. 1000) and then divide it by the size of a page (e.g. 100), that'll give you how many requests/pages you have to execute (e.g. 1000/100 = 10 requests). Then, I'll execute the requests at the same time and wait for the results.
With Cursor based pagination you will have to do sequential requests, however, it doesn't mean that it's slower in all cases. I open this issue so we can add a new column in the results where it compares the performance using requests in parallel.
The text was updated successfully, but these errors were encountered:
One of the cons of using cursors is that it doesn't let you skip pages. In other words, if you want to get page 100, you need to get page 1, 2,3,4 ..., 99.
It's common that Apps get the count of a set and execute multiple requests in parallel to get all the pages. For instance, if I want to iterate over all products, I will execute a count query
products/count.json
, grab that number (e.g. 1000) and then divide it by the size of a page (e.g. 100), that'll give you how many requests/pages you have to execute (e.g. 1000/100 = 10 requests). Then, I'll execute the requests at the same time and wait for the results.With Cursor based pagination you will have to do sequential requests, however, it doesn't mean that it's slower in all cases. I open this issue so we can add a new column in the results where it compares the performance using requests in parallel.
The text was updated successfully, but these errors were encountered: