pg.ddx.io  pgbackrest/pgbackrest GitHub issues and pull requests  
help / color / mirror / Atom feed
From: melancholictheory (@melancholictheory) <noreply+melancholictheory@github.com>
To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>
Subject: Re: [pgbackrest/pgbackrest] PR #2912: Limit the free list to the configured I/O buffer size
Date: Mon, 09 Nov 2026 12:30:02 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2912-c6740094300@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2912@github.com>
References: <gh-pgbackrest-pgbackrest-2912@github.com>

I repeated the #2816 workload on native Linux x86-64 with local MinIO and glibc 2.41. The Intel Xeon E-2388G host reports “Not affected” for Meltdown and does not have PTI active.

The setup was PostgreSQL 18 with 10,000 small tables, a shared full backup with block incremental enabled, and an update to every other table. I ran six differential backups per build, rotating the order, with process-max=1, buffer-size=1MiB, and zstd level 1.

| Build | Median elapsed time | Median minor faults | Median peak summed RssAnon |
| --- | ---: | ---: | ---: |
| #2914 revert | 3.31 s | 293k | 28.3 MiB |
| Original free list | 2.58 s | 24k | 51.3 MiB |
| Single bucket for buffer-size | 2.95 s | 24k | 33.4 MiB |

The single bucket was faster than the revert in all six rounds, with an 11% lower median elapsed time. It used about 18 MiB less peak anonymous RSS than the original free list. This confirms a repeatable elapsed-time benefit for the single bucket on this x86-64 workload.


view thread (20+ messages)  latest in thread

Message-ID: <gh-pgbackrest-pgbackrest-2912-c6740094300@github.com>
Permalink:  ../gh-pgbackrest-pgbackrest-2912-c6740094300@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox