From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox{, -backup} v2 0/2] GC: log progress output for phase 2 S3 datastores
Date: Fri, 23 Jan 2026 14:54:24 +0100 [thread overview]
Message-ID: <299b3a77-f1a3-4081-bb49-a99c83c7a11e@proxmox.com> (raw)
In-Reply-To: <kyxm3fkwmub66dlndk3365fv5lw4gbt3wqs5ekkpth4tbmnqpq@r4g2j527mqhx>
Hi Arthur,
On 1/23/26 2:39 PM, Arthur Bied-Charreton wrote:
>
> Tested-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
>
> I tested these changes on a local MinIO S3 datastore, the rate-limited
> logging output appears at the expected intervals, and the request statistics
> are accurately displayed.
Thanks for testing!
> Just one question maybe: why is sequential consistency needed for the request
> counters? Wouldn't relaxed ordering be sufficient for statistics?
This was done with the intention to maybe use the same counters also for
enforcing soft limits and/or enforce warnings when certain thresholds
have been reached, where stricter ordering might be needed.
_______________________________________________
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:[~2026-01-23 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 10:45 Christian Ebner
2026-01-21 10:45 ` [pbs-devel] [PATCH proxmox v2 1/1] s3-client: add request statistics gathering capabilities Christian Ebner
2026-01-21 10:45 ` [pbs-devel] [PATCH proxmox-backup v2 1/1] GC: log progress output for phase 2 on datastores backed by s3 Christian Ebner
2026-01-23 13:39 ` [pbs-devel] [PATCH proxmox{, -backup} v2 0/2] GC: log progress output for phase 2 S3 datastores Arthur Bied-Charreton
2026-01-23 13:54 ` Christian Ebner [this message]
2026-01-23 14:02 ` Arthur Bied-Charreton
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=299b3a77-f1a3-4081-bb49-a99c83c7a11e@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=a.bied-charreton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.