From: smiler <xlinghust@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Is disk scheduler in VM useful?
Date: Fri, 15 Mar 2013 08:38:13 -0700 (PDT) [thread overview]
Message-ID: <1363361893067-5714870.post@n5.nabble.com> (raw)
Hi all,
I do the experiment in Xen 4.0.1 with Linux 2.6.31.8 using blktap AIO. Two
sequential read applications (sysbench) run on a VM. I compare the
performance of application under AS, noop and CFQ in the domU, respectively
(disk scheduler of dom0 is CFQ). The results of three schedulers are almost
the same. I did not know why AS does not work for sequentail access
applications, even the performance of AS is same as noop in two sequential
applications. In the physical machine, the as is better than noop, cfq when
running two sequential applications.
Does this mean that scheduling I/O requests in VM is not useful?
--
View this message in context: http://xen.1045712.n5.nabble.com/Is-disk-scheduler-in-VM-useful-tp5714870.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
reply other threads:[~2013-03-15 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1363361893067-5714870.post@n5.nabble.com \
--to=xlinghust@gmail.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).