From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Minchan Kim <minchan@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH v2 0/8] zram: switch to crypto api
Date: Tue, 31 May 2016 12:07:08 -0700 [thread overview]
Message-ID: <20160531120708.b887c44f1f7d9bb536ad2c45@linux-foundation.org> (raw)
In-Reply-To: <20160531122918.GA612@swordfish>
On Tue, 31 May 2016 21:29:18 +0900 Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> forgot to attach some benchmarks:
>
> (x86_64, 4GB, zram-perf script)
>
> perf reported run-time fio (max jobs=3)
>
> test-fio-zram-842
> 197.907655282 seconds time elapsed
> 201.623142884 seconds time elapsed
> 226.854291345 seconds time elapsed
> test-fio-zram-DEFLATE
> 253.259516155 seconds time elapsed
> 258.148563401 seconds time elapsed
> 290.251909365 seconds time elapsed
> test-fio-zram-LZ4
> 27.022598717 seconds time elapsed
> 29.580522717 seconds time elapsed
> 33.293463430 seconds time elapsed
> test-fio-zram-LZ4HC
> 56.393954615 seconds time elapsed
> 74.904659747 seconds time elapsed
> 101.940998564 seconds time elapsed
> test-fio-zram-LZO
> 28.155948075 seconds time elapsed
> 30.390036330 seconds time elapsed
> 34.455773159 seconds time elapsed
I'm having trouble understanding the benchmark results. What is being
compared to what and which was faster and how much?
next prev parent reply other threads:[~2016-05-31 19:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 12:20 Sergey Senozhatsky
2016-05-31 12:20 ` [PATCH v2 1/8] zram: rename zstrm find-release functions Sergey Senozhatsky
2016-05-31 12:20 ` [PATCH v2 2/8] zram: switch to crypto compress API Sergey Senozhatsky
2016-05-31 23:40 ` Minchan Kim
2016-05-31 23:44 ` Minchan Kim
2016-06-01 1:17 ` Sergey Senozhatsky
2016-05-31 12:20 ` [PATCH v2 3/8] zram: align zcomp interface to crypto comp API Sergey Senozhatsky
2016-05-31 23:48 ` Minchan Kim
2016-06-01 1:13 ` Sergey Senozhatsky
2016-05-31 12:20 ` [PATCH v2 4/8] zram: use crypto api to check alg availability Sergey Senozhatsky
2016-06-01 0:03 ` Minchan Kim
2016-06-01 1:07 ` Sergey Senozhatsky
2016-06-01 2:27 ` Minchan Kim
2016-06-01 3:17 ` Sergey Senozhatsky
2016-06-01 6:47 ` Minchan Kim
2016-06-01 7:48 ` Sergey Senozhatsky
2016-06-01 14:59 ` Austin S. Hemmelgarn
2016-06-02 2:40 ` Minchan Kim
2016-05-31 12:20 ` [PATCH v2 5/8] zram: cosmetic: cleanup documentation Sergey Senozhatsky
2016-06-01 0:06 ` Minchan Kim
2016-05-31 12:20 ` [PATCH v2 6/8] zram: delete custom lzo/lz4 Sergey Senozhatsky
2016-06-01 0:08 ` Minchan Kim
2016-05-31 12:20 ` [PATCH v2 7/8] zram: add more compression algorithms Sergey Senozhatsky
2016-06-01 0:24 ` Minchan Kim
2016-05-31 12:20 ` [PATCH v2 8/8] zram: drop gfp_t from zcomp_strm_alloc() Sergey Senozhatsky
2016-06-01 0:41 ` Minchan Kim
2016-05-31 12:29 ` [PATCH v2 0/8] zram: switch to crypto api Sergey Senozhatsky
2016-05-31 19:07 ` Andrew Morton [this message]
2016-06-01 0:58 ` Sergey Senozhatsky
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=20160531120708.b887c44f1f7d9bb536ad2c45@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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
all inboxes | Powered by JetHome®