From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>,
Nicolas Frey <n.frey@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox v2 2/3] pbs-api-types: jobs: add {read, verify}-threads to VerificationJobConfig
Date: Fri, 7 Nov 2025 08:47:41 +0100 [thread overview]
Message-ID: <7b58d965-c5cd-499f-bf3f-2a911424d19e@proxmox.com> (raw)
In-Reply-To: <f6ac41cd-0784-42ea-bff2-057f597f45df@proxmox.com>
On 11/6/25 6:43 PM, Thomas Lamprecht wrote:
> Am 06.11.25 um 17:13 schrieb Nicolas Frey:
>> controls the number of parallel threads to read/verify chunks.
>>
>
> Any thoughts on having these options (also) in the datastore config's tuning
> options? No hard feelings for that, just something I asked myself. Can be fine
> to not do now (it's easier to add things later than having to remove them again),
> but might still warrant adding some reasoning for choosing the verification
> config here in the commit message, at least if there's the need for a v3. Could
> be fleeced in on applying otherwise.
Yes, setting this also on a datastore level for global defaults make a
lot of sense indeed. Would allow to run regular verification's (e.g.
immediate verification after backup) with these global defaults and
maybe dial up the number of reads/verifies for a monthly full datastore
verification job, running at a time where there is not much other CPU
and IO load.
Although I'm not sure if we should place these in the tuning options,
they are a bit crowded already. We could add dedicated
`worker-thread-settings` to the datastore config instead? That is, if we
commit to having these kind of knobs exposed for other workers (e.g.
tape) as well.
What's your opinion on that?
_______________________________________________
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-11-07 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 16:13 [pbs-devel] [PATCH proxmox{, -backup} v2 0/7] parallelize chunk reads in verification Nicolas Frey
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox v2 1/3] pbs-api-types: add schema for {worker, read, verify}-threads Nicolas Frey
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox v2 2/3] pbs-api-types: jobs: add {read, verify}-threads to VerificationJobConfig Nicolas Frey
2025-11-06 17:44 ` Thomas Lamprecht
2025-11-07 7:47 ` Christian Ebner [this message]
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox v2 3/3] pbs-api-types: use worker-threads schema for TapeBackupJobSetup Nicolas Frey
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox-backup v2 1/4] api: verify: move chunk loading into parallel handler Nicolas Frey
2025-11-07 8:39 ` Christian Ebner
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox-backup v2 2/4] api: verify: determine the number of threads to use with {read, verify}-threads Nicolas Frey
2025-11-07 9:31 ` Christian Ebner
2025-11-07 9:41 ` Christian Ebner
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox-backup v2 3/4] api: verify: add {read, verify}-threads to update endpoint Nicolas Frey
2025-11-06 16:13 ` [pbs-devel] [PATCH proxmox-backup v2 4/4] ui: verify: add option to set number of threads for job Nicolas Frey
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=7b58d965-c5cd-499f-bf3f-2a911424d19e@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=n.frey@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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