From: Vivek Goyal <vgoyal@redhat.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Jens Axboe <jaxboe@fusionio.com>
Subject: Re: [PATCH 3/3]Subject: CFQ: add think time check for group
Date: Wed, 6 Jul 2011 11:06:28 -0400 [thread overview]
Message-ID: <20110706150628.GD27302@redhat.com> (raw)
In-Reply-To: <1309917520.15392.246.camel@sli10-conroe>
On Wed, Jul 06, 2011 at 09:58:40AM +0800, Shaohua Li wrote:
[..]
> > > [global]
> > > runtime=30
> > > direct=1
> > >
> > > [test1]
> > > cgroup=test1
> > > cgroup_weight=1000
> > > rw=randread
> > > ioengine=libaio
> > > size=500m
> > > runtime=30
> > > directory=/mnt
> > > filename=file1
> > > thinktime=9000
> > >
> > > [test2]
> > > cgroup=test2
> > > cgroup_weight=1000
> > > rw=randread
> > > ioengine=libaio
> > > size=500m
> > > runtime=30
> > > directory=/mnt
> > > filename=file2
> > >
> > > patched base
> > > test1 64k 39k
> > > test2 540k 540k
> > > total 604k 578k
> > >
> > > group1 gets much better throughput because it waits less time.
I don't understand it. Thinktime of group test1 is more than 8ms. So now
we should not be idling on test1. Hence test1 should lose some share and
test2 should gain disk share and overall throughput should go up.
I am wondering why throughput of test2 did not go up?
Also can you run some tests to make sure that disk shares of regular
workloads (thinktime less than 8ms) are not impacted.
Thanks
Vivek
next prev parent reply other threads:[~2011-07-06 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 5:36 [PATCH 3/3]Subject: CFQ: add think time check for group Shaohua Li
2011-07-05 14:31 ` Vivek Goyal
2011-07-06 1:58 ` Shaohua Li
2011-07-06 15:06 ` Vivek Goyal [this message]
2011-07-07 6:08 ` Shaohua Li
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=20110706150628.GD27302@redhat.com \
--to=vgoyal@redhat.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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