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
Coming from Drupal, I would recommend using the shop system Commerce rather than Ubercart for the features you’re looking for. It has already been ported to Backdrop CMS. General...
How to monetize a Backdrop site
When logged in: On a page with a path prefix it shows the language of the prefix. On the front page if I add the path prefix it shows the language of that prefix...
Language negotiation only working when logged in
Hi! The description is still very vague and lacks step-by-step instructions on how to reproduce. It doesn't include the version of Backdrop either, nor a list of contrib modules you are using...
Problems with HTML content and text formats