Many moons ago I filed issue https://www.drupal.org/node/778050 again Drupal. That didn't go anywhere, because the pager was not pluggable and needed to be database-agnostic.
Happily, Backdrop only supports MySQL, so the pager changes should in theory Just Work™. This means that complicated queries no longer need custom count queries and the database doesn't need to run two queries each time a pager is displayed on the site.
I ran a lot of beanchmarks on the original issue and there was no performance degradation for small tables, and improved performance for large tables. You can see details at http://cafuego.net/2010/05/26/fast-paging-real-world
GitHub Issue #:
404
Recent comments
I'll be very happy to test this and will report back.
Database update warning - but no pending updates
For anyone interested in an improvement to the Status report that should help with this, please see this issue and the associated pull request: https://github.com/backdrop/backdrop-issues/...
Database update warning - but no pending updates
@paucku I note from this issue here: https://github.com/backdrop-contrib/domain/issues/71 That you started getting this config formatting after changing the module to what Chat...
I need to understand how active and staging folders work – configuration management