public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Yanni M." <gianni.milo22@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] ZFS configurations, performance and optimization...
Date: Mon, 26 Jul 2021 22:35:02 +0100	[thread overview]
Message-ID: <CACzVk9VcwNAio_QTEaaK-5veLw8VE_xvQDVdR0FnRAG97iaMRw@mail.gmail.com> (raw)
In-Reply-To: <20210726093746.GB3289@sv.lnf.it>

In my opinion, you are not doing something wrong but likely are the
limitations of relatively small raidz1 array (3 disks) and the parity
calculation overhead which both are leading to lower performance compared
to that of the mirrored array. Wherever possible, choose multiple mirrored
vdev configuration (raid10) rather than raidz, as VMs in general tend to be
more interested in IOPS rather than bandwidth (streaming) performance.
If you decide to keep raidz1, then try adding more disks onto it. If you
use zvols for the VMs, try increasing volblocksize from 8k which is the
default, to 16k or 32k.
Personally, I'd add one more disk into the mix and go for 2 vdev mirrored
setup (raid10) and keep the zfs defaults.



On Mon, 26 Jul 2021 at 10:37, Marco Gaiarin <gaio@sv.lnf.it> wrote:

>
> Consider two rather equal servers, both with equal disks (2TB
> rotational drives); one server have a ZFS mirror (two disk), the other
> have a ZFS RAIDZ1, with 3 disks.
>
> Both server are unload, we are moving data in, via single
> Gigabit connection.
>
>
> Moving data into the ZFS mirror lead to a impressive 120 Mbyte/s
> writing speed, with little or no iodelay (1-2 %).
>
> Moving data into ZRAID1 lead to an 60-70 Mbyte/s writing speed, no
> more, and a decent iodelay on the system (8-10 %).
>
> Both seems to me configured equally (eg, for example, no compression).
>
>
> I've read:
>
>
> https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_raid_considerations
>
> but really i'm got a bit lost... there's somewhere a more clear
> explanation of the 'effect', and i hope some parameters to tackle with?
>
>
> Thanks.
>
>
> PS: it is not a problem 'per se', the RAIDZ1 pool could be 'slow', but
>     i've the doubt to have done somthing wrong...
>
> --
> dott. Marco Gaiarin                                     GNUPG Key ID:
> 240A3D66
>   Associazione ``La Nostra Famiglia''
> http://www.lanostrafamiglia.it/
>   Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento
> (PN)
>   marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f
> +39-0434-842797
>
>                 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
>       http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
>         (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>


  reply	other threads:[~2021-07-26 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26  9:37 Marco Gaiarin
2021-07-26 21:35 ` Yanni M. [this message]
2021-07-28 16:35   ` Marco Gaiarin

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=CACzVk9VcwNAio_QTEaaK-5veLw8VE_xvQDVdR0FnRAG97iaMRw@mail.gmail.com \
    --to=gianni.milo22@gmail.com \
    --cc=pve-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal