From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: zram: per-cpu compression streams
Date: Wed, 27 Apr 2016 18:01:40 +0900 [thread overview]
Message-ID: <20160427090139.GA1317@swordfish> (raw)
In-Reply-To: <20160427085408.GA1108@swordfish>
On (04/27/16 17:54), Sergey Senozhatsky wrote:
> #jobs4
> READ: 19948MB/s 20013MB/s
> READ: 17732MB/s 17479MB/s
> WRITE: 630690KB/s 495078KB/s
> WRITE: 1843.2MB/s 2226.9MB/s
> READ: 1603.4MB/s 1846.8MB/s
> WRITE: 1599.4MB/s 1842.2MB/s
> READ: 1547.7MB/s 1740.7MB/s
> WRITE: 1549.2MB/s 1742.4MB/s
> jobs4
> stalled-cycles-frontend 265,519,049,536 ( 64.46%) 221,049,841,649 ( 61.81%)
> stalled-cycles-backend 146,538,881,296 ( 35.57%) 113,774,053,039 ( 31.82%)
> instructions 298,241,854,695 ( 0.72) 278,000,866,874 ( 0.78)
> branches 59,531,800,053 ( 400.919) 55,096,944,109 ( 427.816)
> branch-misses 285,108,083 ( 0.48%) 260,972,185 ( 0.47%)
> seconds elapsed 47.816933840 52.966896478
per-cpu in general looks better in this test (jobs4): less stalls, less
branches, less misses, better fio speeds (except for WRITE: 630690KB/s 495078KB/s).
the system was under pressure, so quite possible that it took more time to kill the
process, thus execution time is in favor of 8 streams test.
-ss
prev parent reply other threads:[~2016-04-27 9:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 8:12 zram: per-cpu compression streams Sergey Senozhatsky
2016-03-24 23:41 ` Minchan Kim
2016-03-25 1:47 ` Sergey Senozhatsky
2016-03-28 3:21 ` Minchan Kim
2016-03-30 8:34 ` Sergey Senozhatsky
2016-03-30 22:12 ` Minchan Kim
2016-03-31 1:26 ` Sergey Senozhatsky
2016-03-31 5:53 ` Minchan Kim
2016-03-31 6:34 ` Sergey Senozhatsky
2016-04-01 15:38 ` Sergey Senozhatsky
2016-04-04 0:27 ` Minchan Kim
2016-04-04 1:17 ` Sergey Senozhatsky
2016-04-18 7:57 ` Sergey Senozhatsky
2016-04-19 8:00 ` Minchan Kim
2016-04-19 8:08 ` Sergey Senozhatsky
2016-04-26 11:23 ` Sergey Senozhatsky
2016-04-27 7:29 ` Minchan Kim
2016-04-27 7:43 ` Sergey Senozhatsky
2016-04-27 7:55 ` Minchan Kim
2016-04-27 8:10 ` Sergey Senozhatsky
2016-04-27 8:54 ` Sergey Senozhatsky
2016-04-27 9:01 ` Sergey Senozhatsky [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=20160427090139.GA1317@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--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