From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v4 proxmox-backup 4/5] garbage collection: generate index file list via datastore iterators
Date: Tue, 25 Mar 2025 13:09:34 +0100 [thread overview]
Message-ID: <86c95ec4-8937-4e2b-aa6e-f41272da0b7a@proxmox.com> (raw)
In-Reply-To: <20250321093202.155899-5-c.ebner@proxmox.com>
Am 21.03.25 um 10:32 schrieb Christian Ebner:
> Instead of iterating over all index files found in the datastore in
> an unstructured manner, use the datastore iterators to logically
> iterate over them as other datastore operations will.
>
> This allows to better distinguish index files in unexpected locations
> from ones in their expected location, warning the user of unexpected
> ones to allow to act on possible missconfigurations. Further, this
> will allow to integrate marking of snapshots with missing chunks as
> incomplete/corrupt more easily.
>
> This now iterates twice over the index files, as indices in
> unexpected locations are still considered by generating the list of
> all index files to be found in the datastore and removing regular
> index files from that list, leaving unexpected ones behind.
Can you also describe the rough changes in terms of time and (peak)
memory used? As replied to patch 5/5 it's probably not too important
to get the perfect reference setup for evaluating this, but to have
one that isn't an obvious extreme (no snapshots, the same snapshots
a hundred times, ...) and describe that setup.
It might be also nice to mention that this is in preparation to get
better cache reuse due to processing snapshots from the same group
closely together.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-03-25 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:31 [pbs-devel] [PATCH v4 proxmox-backup 0/5] fix #5331: GC: avoid multiple atime updates Christian Ebner
2025-03-21 9:31 ` [pbs-devel] [PATCH v4 proxmox-backup 1/5] tools: lru cache: tell if node was already present or newly inserted Christian Ebner
2025-03-21 9:31 ` [pbs-devel] [PATCH v4 proxmox-backup 2/5] garbage collection: format error including anyhow error context Christian Ebner
2025-03-21 9:32 ` [pbs-devel] [PATCH v4 proxmox-backup 3/5] datastore: add helper method to open index reader from path Christian Ebner
2025-03-21 9:32 ` [pbs-devel] [PATCH v4 proxmox-backup 4/5] garbage collection: generate index file list via datastore iterators Christian Ebner
2025-03-25 12:09 ` Thomas Lamprecht [this message]
2025-03-21 9:32 ` [pbs-devel] [PATCH v4 proxmox-backup 5/5] fix #5331: garbage collection: avoid multiple chunk atime updates Christian Ebner
2025-03-25 11:56 ` Thomas Lamprecht
2025-03-25 12:07 ` Thomas Lamprecht
2025-03-25 13:05 ` Christian Ebner
2025-03-26 10:05 ` [pbs-devel] [PATCH v4 proxmox-backup 0/5] fix #5331: GC: avoid multiple " Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86c95ec4-8937-4e2b-aa6e-f41272da0b7a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal