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-backup 4/4] ui: verify: add option to set number of threads for job
Date: Thu, 6 Nov 2025 10:22:16 +0100 [thread overview]
Message-ID: <6bebe9f1-b8d1-4e96-a7bb-30deb71e33a1@proxmox.com> (raw)
In-Reply-To: <20251105155129.517430-6-n.frey@proxmox.com>
Same comment with respect to commit title as for some of the other
patches, a short description on why this is done would be nice. E.g.
Exposes the worker-threads property in the verification job config
window and verify all window so the user can update the values accordingly.
one comment below
On 11/5/25 4:51 PM, Nicolas Frey wrote:
> Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
> ---
> www/window/VerifyAll.js | 12 ++++++++++++
> www/window/VerifyJobEdit.js | 13 +++++++++++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/www/window/VerifyAll.js b/www/window/VerifyAll.js
> index 01bcd63d..82f62aae 100644
> --- a/www/window/VerifyAll.js
> +++ b/www/window/VerifyAll.js
> @@ -80,6 +80,18 @@ Ext.define('PBS.window.VerifyAll', {
> },
> ],
> },
> +
> + {
> + xtype: 'proxmoxintegerfield',
> + name: 'worker-threads',
> + fieldLabel: gettext('# of Worker Threads'),
> + emptyText: '1',
> + minValue: 1,
> + maxValue: 32,
> + cbind: {
> + deleteEmpty: '{!isCreate}',
> + },
> + },
> ],
> },
> ],
> diff --git a/www/window/VerifyJobEdit.js b/www/window/VerifyJobEdit.js
> index e87ca069..7b7a96c4 100644
> --- a/www/window/VerifyJobEdit.js
> +++ b/www/window/VerifyJobEdit.js
> @@ -166,5 +166,18 @@ Ext.define('PBS.window.VerifyJobEdit', {
> },
> },
> ],
> + advancedColumn2: [
> + {
> + xtype: 'proxmoxintegerfield',
> + name: 'worker-threads',
> + fieldLabel: gettext('# of Worker Threads'),
> + emptyText: '1',
> + minValue: 1,
> + maxValue: 32,
> + cbind: {
> + deleteEmpty: '{!isCreate}',
> + },
> + },
> + ]
it would be nice to also delete the value again if set to the default.
Further, just noticed: this now seemingly defaults to 1, which is also
the default for the API schema, but the parallel task instantiation gets
a default of 4 if the value is not set and therefore unwrapped? That
should be made consistent.
> },
> });
_______________________________________________
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-06 9:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:51 [pbs-devel] [PATCH proxmox{, -backup} 0/5] parallelize chunk reads in verification Nicolas Frey
2025-11-05 15:51 ` [pbs-devel] [PATCH proxmox 1/1] pbs-api-types: jobs: verify: add worker-threads to VerificationJobConfig Nicolas Frey
2025-11-06 8:14 ` Christian Ebner
2025-11-05 15:51 ` [pbs-devel] [PATCH proxmox-backup 1/4] api: verify: move chunk loading into parallel handler Nicolas Frey
2025-11-06 8:54 ` Christian Ebner
2025-11-06 9:04 ` Nicolas Frey
2025-11-06 9:26 ` Christian Ebner
2025-11-05 15:51 ` [pbs-devel] [PATCH proxmox-backup 2/4] api: verify: use worker-threads to determine the number of threads to use Nicolas Frey
2025-11-06 9:09 ` Christian Ebner
2025-11-06 9:23 ` Nicolas Frey
2025-11-06 9:32 ` Christian Ebner
2025-11-06 11:22 ` Nicolas Frey
2025-11-06 11:57 ` Christian Ebner
2025-11-05 15:51 ` [pbs-devel] [PATCH proxmox-backup 3/4] api: verify: add worker-threads to update endpoint Nicolas Frey
2025-11-06 9:13 ` Christian Ebner
2025-11-05 15:51 ` [pbs-devel] [PATCH proxmox-backup 4/4] ui: verify: add option to set number of threads for job Nicolas Frey
2025-11-06 9:22 ` Christian Ebner [this message]
2025-11-06 9:25 ` Nicolas Frey
2025-11-06 8:02 ` [pbs-devel] [PATCH proxmox{, -backup} 0/5] parallelize chunk reads in verification 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=6bebe9f1-b8d1-4e96-a7bb-30deb71e33a1@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 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.