From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH 2/2] zram: remove zlib from the list of recommended algorithms
Date: Wed, 13 Sep 2017 16:12:46 +0900 [thread overview]
Message-ID: <20170913071246.GB2975@bbox> (raw)
In-Reply-To: <20170912050005.3247-2-sergey.senozhatsky@gmail.com>
On Tue, Sep 12, 2017 at 02:00:05PM +0900, Sergey Senozhatsky wrote:
> ZSTD tends to outperform deflate/inflate, thus we remove
> zlib from the list of recommended algorithms and recommend
> zstd instead.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Suggested-by: Minchan Kim <minchan@kernel.org>
I did test with my sample data and compared zstd with deflate.
zstd's compress ratio is lower a little bit but compression
speed is much faster 3 times more and decompress speed is too
2 times more. With different data, it is different but overall,
zstd would be better for speed at the cost of a little lower compress
ratio(about 5%) so I believe it's worth to replace deflate.
Thanks for the patch, Sergey.
Acked-by: Minchan Kim <minchan@kernel.org>
next prev parent reply other threads:[~2017-09-13 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 5:00 [PATCH 1/2] zram: add zstd to the supported algorithms list Sergey Senozhatsky
2017-09-12 5:00 ` [PATCH 2/2] zram: remove zlib from the list of recommended algorithms Sergey Senozhatsky
2017-09-12 6:49 ` Minchan Kim
2017-09-12 7:00 ` Sergey Senozhatsky
2017-09-13 7:12 ` Minchan Kim [this message]
2017-09-13 7:16 ` Sergey Senozhatsky
2017-09-13 10:38 ` Adam Borowski
2017-09-14 8:02 ` Minchan Kim
2017-09-13 6:58 ` [PATCH 1/2] zram: add zstd to the supported algorithms list Minchan Kim
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=20170913071246.GB2975@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.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