From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup v5] datastore: make 'filesystem' the default sync-level
Date: Mon, 28 Nov 2022 10:17:28 +0100 [thread overview]
Message-ID: <378cc664-734c-dda8-b9e2-c9f75f35d223@proxmox.com> (raw)
In-Reply-To: <20221104094934.1135932-1-d.csapak@proxmox.com>
Am 04/11/2022 um 10:49 schrieb Dominik Csapak:
> rationale is that it makes the backup much safer than 'none', but does not
> incur a big of a performance hit as 'file'.
>
> here some benchmark:
>
> data to be backed up:
> ~14GiB semi-random test images between 12kiB and 4GiB
> that results in ~11GiB chunks (more than ram available on the target)
>
> PBS setup:
> virtualized (on an idle machine), PBS itself was also idle
> 8 cores (kvm64 on Intel 12700k) and 8 GiB memory
>
> all virtual disks are on LVM with discard and iothread on
> the HDD is a 4TB Seagate ST4000DM000 drive, and the NVME is a 2TB
> Crucial CT2000P5PSSD8
>
> i tested each disk with ext4/xfs/zfs (default created with the gui)
> with 5 runs each, inbetween the caches are flushed and the filesystem synced
> i removed the biggest and smallest result and from the remaining 3
> results built the average (percentage is relative to the 'none' result)
>
> result:
>
> test none filesystem file
> hdd - ext4 125.67s 140.39s (+11.71%) 358.10s (+184.95%)
> hdd - xfs 92.18s 102.64s (+11.35%) 351.58s (+281.41%)
> hdd - zfs 94.82s 104.00s (+9.68%) 309.13s (+226.02%)
> nvme - ext4 60.44s 60.26s (-0.30%) 60.47s (+0.05%)
> nvme - xfs 60.11s 60.47s (+0.60%) 60.49s (+0.63%)
> nvme - zfs 60.83s 60.85s (+0.03%) 60.80s (-0.05%)
>
> So all in all, it does not seem to make a difference for nvme drives,
> for hdds 'filesystem' increases backup time by ~10%, while
> for 'file' it largely depends on the filesystem, but always
> in the range of factor ~3 - ~4
>
> Note that this does not take into account parallel actions, such as gc,
> verify or other backups.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> changes from v4:
> * included benchmark & rationale in the commit message
>
> docs/storage.rst | 4 ++--
> pbs-api-types/src/datastore.rs | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2022-11-28 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 9:49 [pbs-devel] " Dominik Csapak
2022-11-28 9:17 ` 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=378cc664-734c-dda8-b9e2-c9f75f35d223@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal