From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Nicolas Frey <n.frey@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 1/1] pbs-api-types: add verify-job-{read, verify}-threads to tuning options
Date: Fri, 21 Nov 2025 15:15:00 +0100 [thread overview]
Message-ID: <4542d937-1675-48ee-a2a9-7f126aa0bf44@proxmox.com> (raw)
In-Reply-To: <20251121123209.198368-2-n.frey@proxmox.com>
On 11/21/25 1:32 PM, Nicolas Frey wrote:
> to determine the default number of threads to use for verify jobs on
> the datastore level
>
> Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
> ---
> adds it to the tuning options, though it can easily be moved into its
> own setting within the datastore configuration if desired
>
> pbs-api-types/src/datastore.rs | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/pbs-api-types/src/datastore.rs b/pbs-api-types/src/datastore.rs
> index a214ac25..176c0d4a 100644
> --- a/pbs-api-types/src/datastore.rs
> +++ b/pbs-api-types/src/datastore.rs
> @@ -19,7 +19,8 @@ use crate::{
> BACKUP_ID_RE, BACKUP_NS_RE, BACKUP_TIME_RE, BACKUP_TYPE_RE, DATASTORE_NOTIFY_STRING_SCHEMA,
> GC_SCHEDULE_SCHEMA, GROUP_OR_SNAPSHOT_PATH_REGEX_STR, PROXMOX_SAFE_ID_FORMAT,
> PROXMOX_SAFE_ID_REGEX_STR, PRUNE_SCHEDULE_SCHEMA, SHA256_HEX_REGEX, SINGLE_LINE_COMMENT_SCHEMA,
> - SNAPSHOT_PATH_REGEX_STR, UPID,
> + SNAPSHOT_PATH_REGEX_STR, UPID, VERIFY_JOB_READ_THREADS_SCHEMA,
> + VERIFY_JOB_VERIFY_THREADS_SCHEMA,
> };
>
> const_regex! {
> @@ -262,6 +263,14 @@ pub const GC_CACHE_CAPACITY_SCHEMA: Schema =
> schema: GC_CACHE_CAPACITY_SCHEMA,
> optional: true,
> },
> + "verify-job-verify-threads": {
nit: these are user facing and a bit clumsy, especially if to be set via
cli. so maybe `default-verificaton-workers`?
> + schema: VERIFY_JOB_VERIFY_THREADS_SCHEMA,
> + optional: true,
> + },
> + "verify-job-read-threads": {
... same: maybe `default-verification-readers`. But no hard opinion
here, as at least your suggestions make the correlation to the now
pre-existing per verify job configuration parameters clearer.
> + schema: VERIFY_JOB_READ_THREADS_SCHEMA,
> + optional: true,
> + },
> },
> )]
> #[derive(Serialize, Deserialize, Default)]
> @@ -279,6 +288,10 @@ pub struct DatastoreTuning {
> pub gc_atime_cutoff: Option<usize>,
> #[serde(skip_serializing_if = "Option::is_none")]
> pub gc_cache_capacity: Option<usize>,
> + #[serde(skip_serializing_if = "Option::is_none")]
> + pub verify_job_verify_threads: Option<usize>,
> + #[serde(skip_serializing_if = "Option::is_none")]
> + pub verify_job_read_threads: Option<usize>,
> }
>
> pub const DATASTORE_TUNING_STRING_SCHEMA: Schema = StringSchema::new("Datastore tuning options")
_______________________________________________
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-21 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 12:32 [pbs-devel] [RFC/PATCH proxmox{, -backup} 0/5] tuning: verify: add verify job thread options Nicolas Frey
2025-11-21 12:32 ` [pbs-devel] [PATCH proxmox 1/1] pbs-api-types: add verify-job-{read, verify}-threads to tuning options Nicolas Frey
2025-11-21 14:15 ` Christian Ebner [this message]
2025-11-21 12:32 ` [pbs-devel] [PATCH proxmox-backup 1/4] datastore: add new thread settings " Nicolas Frey
2025-11-21 14:15 ` Christian Ebner
2025-11-21 12:32 ` [pbs-devel] [PATCH proxmox-backup 2/4] verify: use tuning options' thread settings for {verify, read}-threads Nicolas Frey
2025-11-21 12:32 ` [pbs-devel] [PATCH proxmox-backup 3/4] ui: tuning: make verify-job-{read, verify}-threads configurable Nicolas Frey
2025-11-21 12:32 ` [pbs-devel] [PATCH proxmox-backup 4/4] ui: verify: fetch default {read, verify} thread values from tuning options Nicolas Frey
2025-11-21 14:15 ` [pbs-devel] [RFC/PATCH proxmox{, -backup} 0/5] tuning: verify: add verify job thread options 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=4542d937-1675-48ee-a2a9-7f126aa0bf44@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=n.frey@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