From: Fengguang Wu <fengguang.wu@intel.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, Tao Ma <tm@tao.ma>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: readahead: make context readahead more conservative
Date: Mon, 19 Aug 2013 10:05:47 +0800 [thread overview]
Message-ID: <20130819020547.GA11775@localhost> (raw)
In-Reply-To: <52117BED.7000909@cn.fujitsu.com>
On Mon, Aug 19, 2013 at 09:59:09AM +0800, Miao Xie wrote:
> Hi, everyone
>
> On Thu, 8 Aug 2013 16:54:18 +0800, Fengguang Wu wrote:
> > This helps performance on moderately dense random reads on SSD.
> >
> > Transaction-Per-Second numbers provided by Taobao:
> >
> > QPS case
> > -------------------------------------------------------
> > 7536 disable context readahead totally
> > w/ patch: 7129 slower size rampup and start RA on the 3rd read
> > 6717 slower size rampup
> > w/o patch: 5581 unmodified context readahead
> >
> > Before, readahead will be started whenever reading page N+1 when it
> > happen to read N recently. After patch, we'll only start readahead
> > when *three* random reads happen to access pages N, N+1, N+2. The
> > probability of this happening is extremely low for pure random reads,
> > unless they are very dense, which actually deserves some readahead.
> >
> > Also start with a smaller readahead window. The impact to interleaved
> > sequential reads should be small, because for a long run stream, the
> > the small readahead window rampup phase is negletable.
> >
> > The context readahead actually benefits clustered random reads on HDD
> > whose seek cost is pretty high. However as SSD is increasingly used
> > for random read workloads it's better for the context readahead to
> > concentrate on interleaved sequential reads.
> >
> > Another SSD rand read test from Miao
> >
> > # file size: 2GB
> > # read IO amount: 625MB
> > sysbench --test=fileio \
> > --max-requests=10000 \
> > --num-threads=1 \
> > --file-num=1 \
> > --file-block-size=64K \
> > --file-test-mode=rndrd \
> > --file-fsync-freq=0 \
> > --file-fsync-end=off run
> >
> > shows the performance of btrfs grows up from 69MB/s to 121MB/s,
> > ext4 from 104MB/s to 121MB/s.
>
> I did the same test on the hard disk recently,
> for btrfs, there is ~5% regression(10.65MB/s -> 10.09MB/s),
> for ext4, the performance grows up a bit.(9.98MB/s -> 10.04MB/s).
> (I run the test for 4 times, and the above result is the average of the test.)
>
> Any comment?
Thanks for the tests! Minor regressions on the HDD cases are expected.
Since random read workloads are migrating to SSD as it becomes cheaper
and larger, it seems a good tradeoff to optimize for random read
performance on SSD.
Thanks,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, Tao Ma <tm@tao.ma>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: readahead: make context readahead more conservative
Date: Mon, 19 Aug 2013 10:05:47 +0800 [thread overview]
Message-ID: <20130819020547.GA11775@localhost> (raw)
In-Reply-To: <52117BED.7000909@cn.fujitsu.com>
On Mon, Aug 19, 2013 at 09:59:09AM +0800, Miao Xie wrote:
> Hi, everyone
>
> On Thu, 8 Aug 2013 16:54:18 +0800, Fengguang Wu wrote:
> > This helps performance on moderately dense random reads on SSD.
> >
> > Transaction-Per-Second numbers provided by Taobao:
> >
> > QPS case
> > -------------------------------------------------------
> > 7536 disable context readahead totally
> > w/ patch: 7129 slower size rampup and start RA on the 3rd read
> > 6717 slower size rampup
> > w/o patch: 5581 unmodified context readahead
> >
> > Before, readahead will be started whenever reading page N+1 when it
> > happen to read N recently. After patch, we'll only start readahead
> > when *three* random reads happen to access pages N, N+1, N+2. The
> > probability of this happening is extremely low for pure random reads,
> > unless they are very dense, which actually deserves some readahead.
> >
> > Also start with a smaller readahead window. The impact to interleaved
> > sequential reads should be small, because for a long run stream, the
> > the small readahead window rampup phase is negletable.
> >
> > The context readahead actually benefits clustered random reads on HDD
> > whose seek cost is pretty high. However as SSD is increasingly used
> > for random read workloads it's better for the context readahead to
> > concentrate on interleaved sequential reads.
> >
> > Another SSD rand read test from Miao
> >
> > # file size: 2GB
> > # read IO amount: 625MB
> > sysbench --test=fileio \
> > --max-requests=10000 \
> > --num-threads=1 \
> > --file-num=1 \
> > --file-block-size=64K \
> > --file-test-mode=rndrd \
> > --file-fsync-freq=0 \
> > --file-fsync-end=off run
> >
> > shows the performance of btrfs grows up from 69MB/s to 121MB/s,
> > ext4 from 104MB/s to 121MB/s.
>
> I did the same test on the hard disk recently,
> for btrfs, there is ~5% regression(10.65MB/s -> 10.09MB/s),
> for ext4, the performance grows up a bit.(9.98MB/s -> 10.04MB/s).
> (I run the test for 4 times, and the above result is the average of the test.)
>
> Any comment?
Thanks for the tests! Minor regressions on the HDD cases are expected.
Since random read workloads are migrating to SSD as it becomes cheaper
and larger, it seems a good tradeoff to optimize for random read
performance on SSD.
Thanks,
Fengguang
next prev parent reply other threads:[~2013-08-19 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 8:54 readahead: make context readahead more conservative Fengguang Wu
2013-08-08 8:54 ` Fengguang Wu
2013-08-19 1:59 ` Miao Xie
2013-08-19 1:59 ` Miao Xie
2013-08-19 2:05 ` Fengguang Wu [this message]
2013-08-19 2:05 ` Fengguang Wu
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=20130819020547.GA11775@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miaox@cn.fujitsu.com \
--cc=tm@tao.ma \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.