--- Begin Message ---
Hi,
On Thu, 2025-07-03 at 10:57 +0200, Dominik Csapak wrote:
> Hi,
>
> On 7/3/25 10:29, Adam Kalisz via pve-devel wrote:
> > Hi,
> >
> > On Friday I have submitted the patch with a slight edit to allow
> > setting the number of threads from an environment variable.
> >
>
Hi,
On 7/3/25 10:29, Adam Kalisz via pve-devel wrote:
Hi,
On Friday I have submitted the patch with a slight edit to allow
setting the number of threads from an environment variable.
Yes, we saw, thanks for tackling this.
On Tue, 2025-06-24 at 12:43 +0200, Fabian Grünbichler wrote:
Adam K
--- Begin Message ---
Hi,
On Friday I have submitted the patch with a slight edit to allow
setting the number of threads from an environment variable.
On Tue, 2025-06-24 at 12:43 +0200, Fabian Grünbichler wrote:
>
> > Adam Kalisz hat am 24.06.2025 12:22
> > CEST geschrieben:
> > Hi Fabian,
>
>
--- Begin Message ---
Hi Alexandre,
yes, having configurable CONCURRENT_REQUESTS and max_blocking_threads
would be great. However we would need to wire it up all the way to
qmrestore or similar or ensure it is read from some env vars. I didn't
feel confident to introduce this kind of infrastructur
> Adam Kalisz hat am 24.06.2025 12:22 CEST
> geschrieben:
> Hi Fabian,
CCing the list again, assuming it got dropped by accident.
> the CPU usage is higher, I see about 400% for the restore process. I
> didn't investigate the original much because it's unbearably slow.
>
> Yes, having configu
--- Begin Message ---
Hi,
nice work !
Could it be possible to have an option to configure the
CONCURRENT_REQUESTS ?
(to avoid to put too much load on slow spinning storage)
Message initial
De: Adam Kalisz
À: pve-devel@lists.proxmox.com
Objet: Discussion of major PBS rest
> Adam Kalisz via pve-devel hat am 23.06.2025
> 18:10 CEST geschrieben:
> Hi list,
Hi!
> before I go through all the hoops to submit a patch I wanted to discuss
> the current form of the patch that can be found here:
>
> https://github.com/NOT-NULL-Makers/proxmox-backup-qemu/commit/e91f09cfd1
