fast-paginate
fast_page
Our great sponsors
| fast-paginate | fast_page | |
|---|---|---|
| 4 | 2 | |
| 1,149 | 292 | |
| 3.1% | 1.4% | |
| 0.0 | 2.9 | |
| 18 days ago | 9 months ago | |
| PHP | Ruby | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fast-paginate
-
We switched to cursor-based pagination
There are ways to mitigate the (although not eliminate) the slowing down of offset/limit pagination in later pages. The technique is called a "deferred join" and it is most effective in MySQL. The basic idea is to paginate as little data as necessary, and then do a self-join to get the rest of the data for a single page.
You can read more about it here: https://aaronfrancis.com/2022/efficient-pagination-using-def... or here https://planetscale.com/blog/fastpage-faster-offset-paginati....
There are libraries for Laravel (https://github.com/hammerstonedev/fast-paginate) and Rails (https://github.com/planetscale/fast_page) as well!
Cursor based pagination is wonderful, but sometimes you're stuck with offset/limit for whatever reason. Might as well make it fast.
-
Faster offset pagination for Rails apps
The PlanetScale team puts out incredible engineering content. Congrats on the release!
If you're using Laravel, there's a package that you can use to achieve the same effect: https://github.com/hammerstonedev/fast-paginate
- Faster offset / limit pagination for Laravel
- hammerstonedev/fast-paginate: A fast implementation of offset/limit pagination for Laravel.
fast_page
-
We switched to cursor-based pagination
There are ways to mitigate the (although not eliminate) the slowing down of offset/limit pagination in later pages. The technique is called a "deferred join" and it is most effective in MySQL. The basic idea is to paginate as little data as necessary, and then do a self-join to get the rest of the data for a single page.
You can read more about it here: https://aaronfrancis.com/2022/efficient-pagination-using-def... or here https://planetscale.com/blog/fastpage-faster-offset-paginati....
There are libraries for Laravel (https://github.com/hammerstonedev/fast-paginate) and Rails (https://github.com/planetscale/fast_page) as well!
Cursor based pagination is wonderful, but sometimes you're stuck with offset/limit for whatever reason. Might as well make it fast.
-
Faster offset pagination for Rails apps
In both Django and Rails, passing a QuerySet or ActiveRecord::Relation as an argument to a filter/where creates a subquery - in this case, https://github.com/planetscale/fast_page/blob/main/lib/fast_... creates SELECT ... WHERE id IN (SELECT id FROM ...).
So it's not exactly an inner join, but in theory it will be optimized to the same query plan as an inner join. That said, https://stackoverflow.com/questions/2577174/join-vs-sub-quer... has lots of commentary on why this shouldn't be depended on.
What are some alternatives?
Laravel - Laravel is a web application framework with expressive, elegant syntax. We’ve already laid the foundation for your next big idea — freeing you to create without sweating the small things.
Scenic - Versioned database views for Rails