From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox{,-backup} v8 00/10] fix #4182: concurrent group pull/push support for sync jobs
Date: Wed, 22 Apr 2026 21:23:36 +0200 [thread overview]
Message-ID: <177688579422.1297506.10413901646965954565.b4-ty@b4> (raw)
In-Reply-To: <20260422131820.769620-1-c.ebner@proxmox.com>
On Wed, 22 Apr 2026 15:18:10 +0200, Christian Ebner wrote:
> Syncing contents from/to a remote source via a sync job suffers from
> low throughput on high latency networks because of limitations by the
> HTTP/2 connection, as described in [0]. To improve, syncing multiple
> groups in parallel by establishing multiple reader instances has been
> suggested.
>
> This patch series implements the functionality by adding the sync job
> configuration property `worker-threads`, allowing to define the
> number of groups pull/push tokio tasks to be executed in parallel on
> the runtime during each job.
>
> [...]
Applied, with some minor follow-ups, thanks!
[1/9] tools: implement buffered logger for concurrent log messages
commit: e842d62d9cf169058b19197f08dac72aebfbedeb
[2/9] tools: add bounded join set to run concurrent tasks bound by limit
commit: 75cd11b19e2041f10957405fec1372082926226d
[3/9] api: config/sync: add optional `worker-threads` property
commit: 8711d4552961d8b70c9b592a79461e8dabad9f28
[4/9] fix #4182: server: sync: allow pulling backup groups in parallel
commit: fbff37959849ff79780622d68ac86ee6c74cb7b0
[5/9] server: pull: prefix log messages and add error context
commit: 44e682c7892424e64797fb0a958e63fb29e3d52f
[6/9] server: sync: allow pushing groups concurrently
commit: 3b4cf51e727e38a99eb0277b44eb7efd73422aab
[7/9] server: push: prefix log messages and add additional logging
commit: 3be2b6f6073b1a066ddb4736fb05bc118151d6c6
[8/9] sync: move in-progress snapshot filter to helper and use log line sender
commit: 38caf283dc69eef15625304a234a21ce4c3ef97e
[9/9] ui: expose group worker setting in sync job edit window
commit: cf09063fc5ebd8134941c98eb6ebd69af84da393
prev parent reply other threads:[~2026-04-22 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 13:18 [PATCH proxmox{,-backup} v8 00/10] fix #4182: concurrent group pull/push support for sync jobs Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox v8 01/10] pbs api types: add `worker-threads` to sync job config Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 02/10] tools: implement buffered logger for concurrent log messages Christian Ebner
2026-04-22 17:25 ` Thomas Lamprecht
2026-04-22 13:18 ` [PATCH proxmox-backup v8 03/10] tools: add bounded join set to run concurrent tasks bound by limit Christian Ebner
2026-04-22 17:32 ` Thomas Lamprecht
2026-04-22 20:19 ` Thomas Lamprecht
2026-04-22 13:18 ` [PATCH proxmox-backup v8 04/10] api: config/sync: add optional `worker-threads` property Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 05/10] fix #4182: server: sync: allow pulling backup groups in parallel Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 06/10] server: pull: prefix log messages and add error context Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 07/10] server: sync: allow pushing groups concurrently Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 08/10] server: push: prefix log messages and add additional logging Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 09/10] sync: move in-progress snapshot filter to helper and use log line sender Christian Ebner
2026-04-22 13:18 ` [PATCH proxmox-backup v8 10/10] ui: expose group worker setting in sync job edit window Christian Ebner
2026-04-22 19:23 ` Thomas Lamprecht [this message]
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=177688579422.1297506.10413901646965954565.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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.