From: Ingo Molnar <mingo@elte.hu>
To: Prasad Joshi <prasadjoshi124@gmail.com>
Cc: kvm@vger.kernel.org, penberg@kernel.org, asias.hejun@gmail.com,
gorcunov@gmail.com, levinsasha928@gmail.com,
chaitanyakulkarni15@gmail.com, ashwini.kulkarni@gmail.com
Subject: Re: [PATCH v2] kvm tools: Add QCOW level2 caching support
Date: Thu, 2 Jun 2011 11:16:17 +0200 [thread overview]
Message-ID: <20110602091617.GA9615@elte.hu> (raw)
In-Reply-To: <20110602072850.GC2150@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> This introduces a ~1msec delay and thus simulates IO, but the
> delays are *constant* [make sure you use a high-res timers kernel],
> so they do not result in nearly as much measurement noise as real
> block IO does.
>
> The IO delays will still be there, so any caching advantages (and
> CPU overhead reductions) will be measurable very clearly.
>
> This way you are basically 'emulating' a real disk drive but you
> will emulate uniform latencies, which makes measurements a lot more
> reliable - while still relevant to the end result.
>
> So if under such a measurement model you can prove an improvement
> with a patch, that improvement will be there with real disks as
> well - just harder to prove.
Another risk that the current situation carries in itself, beyond
making it more difficult to measure improvements, is that based on a
"bad" Bonnie outlier or artifact you might throw away a perfectly
good change accidentally!
So whenever you think you are fighting noise you need to improve your
measurements, as entropy is a pretty tough opponent to beat.
Thanks,
Ingo
prev parent reply other threads:[~2011-06-02 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 19:26 [PATCH v2] kvm tools: Add QCOW level2 caching support Prasad Joshi
2011-06-02 7:28 ` Ingo Molnar
2011-06-02 8:36 ` Prasad Joshi
2011-06-02 8:57 ` Ingo Molnar
2011-06-02 16:59 ` Prasad Joshi
2011-06-02 9:16 ` Ingo Molnar [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=20110602091617.GA9615@elte.hu \
--to=mingo@elte.hu \
--cc=ashwini.kulkarni@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=chaitanyakulkarni15@gmail.com \
--cc=gorcunov@gmail.com \
--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