From: Adam Kalisz <adam.kalisz@notnullmakers.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: [pbs-devel] Speedups get detailed publicity
Date: Tue, 12 Aug 2025 12:57:07 +0200 [thread overview]
Message-ID: <fc78e14f7e3b7a8e265a6e8ee883892a2d50b3ee.camel@notnullmakers.com> (raw)
In-Reply-To: <mailman.725.1754658515.367.pve-devel@lists.proxmox.com>
Hello lists,
the recent backup restore speedups got some detailed publicity. Jan
Sedlák of Lupa.cz asked me about all the little details and it got into
the article almost without editing. Please excuse the title, it's not
my doing, this was a global effort with people helping with testing
even as far as the USA.
https://www.lupa.cz/clanky/cesi-vyrazne-zrychlili-obnovu-dat-u-rostouci-konkurence-vmwaru-aktualizaci-dali-zdarma-vsem/
Here is a link to the Google Translate translation into English:
https://www-lupa-cz.translate.goog/clanky/cesi-vyrazne-zrychlili-obnovu-dat-u-rostouci-konkurence-vmwaru-aktualizaci-dali-zdarma-vsem/?_x_tr_sl=cs&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp
Thank you Dominik and everybody else for the work on this and
developing Proxmox into a platform, where even smaller changes have a
large impact.
Adam
_______________________________________________
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-08-12 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 11:23 [pbs-devel] Chunk verification speedup discussion, similar speedup opportunities elsewhere Adam Kalisz
2025-07-25 12:46 ` Fabian Grünbichler
2025-07-28 13:14 ` Adam Kalisz
2025-07-28 13:22 ` Fabian Grünbichler
2025-08-08 13:08 ` Adam Kalisz
[not found] ` <mailman.725.1754658515.367.pve-devel@lists.proxmox.com>
2025-08-12 10:57 ` Adam Kalisz [this message]
2025-07-25 15:03 ` Thomas Lamprecht
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=fc78e14f7e3b7a8e265a6e8ee883892a2d50b3ee.camel@notnullmakers.com \
--to=adam.kalisz@notnullmakers.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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