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
Recent comments
Hi Kevin I am interested assisting you developing a theme by cloning feature from existing WordPress website. Please let me know your suitable time to discuss further...
Create a theme from existing website
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Backdrop CMS Core Priorities
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things? The link to a Zulip thread in this initial post leads to an internal one, but there's...
Backdrop CMS Core Priorities