From: Ingo Molnar <mingo@elte.hu>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: penberg@kernel.org, john@jfloren.net, kvm@vger.kernel.org,
asias.hejun@gmail.com, gorcunov@gmail.com,
prasadjoshi124@gmail.com
Subject: Re: [PATCH v2 1/4] kvm tools: Add ioeventfd support
Date: Fri, 27 May 2011 18:52:57 +0200 [thread overview]
Message-ID: <20110527165257.GA4356@elte.hu> (raw)
In-Reply-To: <1306513120-28794-1-git-send-email-levinsasha928@gmail.com>
* Sasha Levin <levinsasha928@gmail.com> wrote:
> Benchmarks ran on a seperate (non boot) 1GB virtio-blk device,
> formatted as ext4, using bonnie++.
>
> cmd line:
> # bonnie++ -d temp/ -c 2 -s 768 -u 0
>
> Before:
> Version 1.96 ------Sequential Output------ --Sequential Input- --Random-
> Concurrency 2 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
> tux 768M 498 99 381127 74 269712 48 2871 99 717109 50 +++++ +++
> Latency 18368us 31063us 21281us 3017us 6875us 251ms
> Version 1.96 ------Sequential Create------ --------Random Create--------
> tux -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
> 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
> Latency 148us 588us 2792us 1547us 1543us 218us
>
> After:
> Version 1.96 ------Sequential Output------ --Sequential Input- --Random-
> Concurrency 2 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
> tux 768M 499 99 459779 73 350689 54 2997 99 860395 58 +++++ +++
> Latency 17194us 14619us 26358us 4055us 7890us 44122us
> Version 1.96 ------Sequential Create------ --------Random Create--------
> tux -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
> 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
> Latency 135us 567us 2564us 134us 1500us 231us
In such cases it would *really* be useful, in addition of dumping
80-100 raw numbers to summarize results and compare them for the
reader, as i suspect you've done already? Please don't keep it a
secret and don't force the reader to compare two tables with 80+ raw
numbers! :-)
Something like:
" In short, block writes are 20% faster, block reads are 19.9%
faster, seeks got 16% faster. None of the operations got slower. "
Thanks,
Ingo
next prev parent reply other threads:[~2011-05-27 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 16:18 [PATCH v2 1/4] kvm tools: Add ioeventfd support Sasha Levin
2011-05-27 16:18 ` [PATCH v2 2/4] kvm tools: Use ioeventfd in virtio-blk Sasha Levin
2011-05-27 16:18 ` [PATCH v2 3/4] kvm tools: Use ioeventfd in virtio-net Sasha Levin
2011-05-29 12:51 ` Ingo Molnar
2011-05-30 23:53 ` Asias He
2011-05-31 7:18 ` Pekka Enberg
2011-05-31 16:32 ` Sasha Levin
2011-06-01 1:41 ` Asias He
2011-06-01 6:35 ` Sasha Levin
2011-06-01 11:11 ` Asias He
2011-05-27 16:18 ` [PATCH v2 4/4] kvm tools: Use ioeventfd in virtio-rng Sasha Levin
2011-05-27 16:52 ` Ingo Molnar [this message]
2011-05-29 11:55 ` [PATCH v2 1/4] kvm tools: Add ioeventfd support Pekka Enberg
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=20110527165257.GA4356@elte.hu \
--to=mingo@elte.hu \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=john@jfloren.net \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@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