Consider using more performant pagination using a pointer to last ID

[ihorvorotnov]

Is your enhancement related to a problem? Please describe.

Page based pagination using slicing is convenient but also not the most performant option due to how GROQ works. Quoting Sanity:

While GROQ makes this super easy, this is actually surprisingly inefficient.

Generally, you can expect slicing performance to be roughly linear relative to the slice range. For example, if the range 100...200 takes 5ms to run, then you can expect 200...300 to take about 10ms, 300...400 to take 15ms, and so on.

This guide provides more details and suggests a more efficient approach: https://www.sanity.io/docs/developer-guides/paginating-with-groq

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[av3nger]

I have ran performance profiling on 15k posts and tested a few approaches. Unfortunately, don't think there's a performant way to make this work. Quote from the link posted above:

The main downside to filtering is that there's no way to easily jump to any page number — there's no random access. In order to render the right page, we need to have visited its preceding pages.

Which means that once we start using "1 2 3 4 5 6 ... Next" type of pagination, clicking on anything other than "Next" will require making that same query to fetch the reference post to use in the filter.