all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	Dietmar Maurer <dietmar@proxmox.com>,
	Geoff Seeley <gseeley@gmail.com>
Subject: Re: [PVE-User] PBS and ZFS Pools Compression?
Date: Fri, 9 Apr 2021 01:51:09 +0200	[thread overview]
Message-ID: <9cd163da-e7b6-f3cf-5537-f601babcaba0@web.de> (raw)
In-Reply-To: <1052148244.1615.1617905219488@webmail.proxmox.com>

i know that there was smartcompression feature in nexenta:

https://openzfs.org/w/images/4/4d/Compression-Saso_Kiselkov.pdf

afaik, it does not exist in zfsonlinux/openzfs.

on my system, i'm getting

- <250MB/s when writing uncompressible data to zfs pool with lz4 enabled

and

- >450MB/s when writing uncompressible data to zfs pool without compression

regards
roland

Am 08.04.21 um 20:06 schrieb Dietmar Maurer:
>> This is a good article on the subject:
>> https://klarasystems.com/articles/openzfs1-understanding-transparent-compression/
> Can't find where the explain it. ZFS magically detects if data is compressible?
> Please can someone give me a hint how they do that?
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>



  reply	other threads:[~2021-04-08 23:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 18:06 Dietmar Maurer
2021-04-08 23:51 ` Roland [this message]
2021-04-09  6:54 ` Fabian Grünbichler
     [not found] <mailman.181.1617896884.359.pve-user@lists.proxmox.com>
2021-04-08 16:22 ` Geoff Seeley
  -- strict thread matches above, loose matches on Subject: below --
2021-04-08 15:47 Dietmar Maurer
2021-04-08 13:06 Lindsay Mathieson
2021-04-08 13:12 ` Roland
2021-04-08 13:13   ` Lindsay Mathieson
2021-04-08 15:19     ` Mikhail

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=9cd163da-e7b6-f3cf-5537-f601babcaba0@web.de \
    --to=devzero@web.de \
    --cc=dietmar@proxmox.com \
    --cc=gseeley@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 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