From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Adam Kalisz <adam.kalisz@notnullmakers.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere
Date: Fri, 25 Jul 2025 17:03:44 +0200 [thread overview]
Message-ID: <1d041343-39be-4d90-8553-6d4fa82e4e2b@proxmox.com> (raw)
In-Reply-To: <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com>
Am 25.07.25 um 13:24 schrieb Adam Kalisz:
> I missed whether the chunk verification speedup when loading chunks got
> applied or whether it was somehow included in the S3-like storage
> option change set.
btw. had a quick talk with Dominik about this topic, while having the
possibility for this would be nice, server side parallelism is a different
thing than client-side, as being able to starve the rest of the system
of all available IO is much easier possible in the server-side case, as
there is currently no knob to enforce some kind of pacing or maximum
bandwidth like the bandwidth limits that client can be enforced too.
So the mentioned series should IMO only be applied if it can be opted
out, or, better in the long term, a pacing/IO bandwidth limit can be
enforced. That is naturally a big amount of work, mostly in evaluating
different options and deciding for what can make sense, that's why I
mentioned that being able to opt-out could be enough, then admins
could at least keep the status quo.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next parent reply other threads:[~2025-07-25 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ac072513fdb726fd0e22fbc79425537dcf63a41.camel@notnullmakers.com>
2025-07-25 15:03 ` Thomas Lamprecht [this message]
[not found] ` <1753447301.win4nv1cia.astroid@yuna.none>
2025-07-28 13:14 ` Adam Kalisz via pve-devel
[not found] ` <874cbfc3d659edb7c8ebdda71e77530e437065a2.camel@notnullmakers.com>
2025-07-28 13:22 ` Fabian Grünbichler
2025-08-08 13:08 ` Adam Kalisz via pve-devel
2025-08-12 10:57 ` [pve-devel] Speedups get detailed publicity Adam Kalisz via pve-devel
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=1d041343-39be-4d90-8553-6d4fa82e4e2b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=adam.kalisz@notnullmakers.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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