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
Sorry - it is the field_group module. However, last night I switched off proxying to the site and proved to Cloudflare Support that it was NOT a Backdrop issue. After a thorough...
Cloudflare specific advice needed [SOLVED]
@ian I am getting lost what module are you using that is version 1.x-1.6.0 and 1.x-1.7.0 ?
Cloudflare specific advice needed [SOLVED]
I'm also now getting a 403 when trying to access admin/reports/updates - it seems to be Backdrop generated but there is nothing in the Recent Log messages other than my login as admin...
Cloudflare specific advice needed [SOLVED]