From: Mel Gorman <mgorman@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Linux-FSDevel <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>,
Jens Axboe <axboe@kernel.dk>, Mel Gorman <mgorman@suse.de>
Subject: [PATCH 1/4] cfq: Increase default value of target_latency
Date: Wed, 18 Jun 2014 09:23:24 +0100 [thread overview]
Message-ID: <1403079807-24690-2-git-send-email-mgorman@suse.de> (raw)
In-Reply-To: <1403079807-24690-1-git-send-email-mgorman@suse.de>
The existing CFQ default target_latency results in very poor performance
for larger numbers of threads doing sequential reads. While this can be
easily described as a tuning problem for users, it is one that is tricky
to detect. This patch the default on the assumption that people with access
to expensive fast storage also know how to tune their IO scheduler.
The following is from tiobench run on a mid-range desktop with a single
spinning disk.
3.16.0-rc1 3.16.0-rc1 3.0.0
vanilla cfq600 vanilla
Mean SeqRead-MB/sec-1 121.88 ( 0.00%) 121.60 ( -0.23%) 134.59 ( 10.42%)
Mean SeqRead-MB/sec-2 101.99 ( 0.00%) 102.35 ( 0.36%) 122.59 ( 20.20%)
Mean SeqRead-MB/sec-4 97.42 ( 0.00%) 99.71 ( 2.35%) 114.78 ( 17.82%)
Mean SeqRead-MB/sec-8 83.39 ( 0.00%) 90.39 ( 8.39%) 100.14 ( 20.09%)
Mean SeqRead-MB/sec-16 68.90 ( 0.00%) 77.29 ( 12.18%) 81.64 ( 18.50%)
As expected, the performance increases for larger number of threads although
still far short of 3.0-vanilla. A concern with a patch like this is that
it would hurt IO latencies but the iostat figures still look reasonable
3.16.0-rc1 3.16.0-rc1 3.0.0
vanilla cfq600 vanilla
Mean sda-avgqz 912.29 939.89 1000.70
Mean sda-await 4268.03 4403.99 4887.67
Mean sda-r_await 79.42 80.33 108.53
Mean sda-w_await 13073.49 11038.81 11599.83
Max sda-avgqz 2194.84 2215.01 2626.78
Max sda-await 18157.88 17586.08 24971.00
Max sda-r_await 888.40 874.22 5308.00
Max sda-w_await 212563.59 190265.33 177698.47
Average read waiting times are barely changed and still short of the
3.0-vanilla kresult. The worst-case read wait times are also acceptable
and far better than 3.0.
Signed-off-by: Mel Gorman <mgorman@suse.de>
---
block/cfq-iosched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index cadc378..34b9d8b 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
@@ -32,7 +32,7 @@ static int cfq_slice_async = HZ / 25;
static const int cfq_slice_async_rq = 2;
static int cfq_slice_idle = HZ / 125;
static int cfq_group_idle = HZ / 125;
-static const int cfq_target_latency = HZ * 3/10; /* 300 ms */
+static const int cfq_target_latency = HZ * 6/10; /* 600 ms */
static const int cfq_hist_divisor = 4;
/*
--
1.8.4.5
--
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>
next prev parent reply other threads:[~2014-06-18 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 8:23 [PATCH 0/4] Improve sequential read throughput Mel Gorman
2014-06-18 8:23 ` Mel Gorman [this message]
2014-06-19 18:38 ` [PATCH 1/4] cfq: Increase default value of target_latency Jeff Moyer
2014-06-19 21:42 ` Dave Chinner
2014-06-20 11:30 ` Mel Gorman
2014-06-21 0:39 ` Dave Chinner
2014-06-20 11:28 ` Mel Gorman
2014-06-18 8:23 ` [PATCH 2/4] mm: pagemap: Avoid unnecessary overhead when tracepoints are deactivated Mel Gorman
2014-06-18 8:23 ` [PATCH 3/4] mm: page_alloc: Reset fair zone allocation policy when batch counts are expired Mel Gorman
2014-06-18 20:01 ` Johannes Weiner
2014-06-18 21:57 ` Mel Gorman
2014-06-19 18:18 ` Johannes Weiner
2014-06-18 8:23 ` [PATCH 4/4] mm: page_alloc: Reduce cost of dirty zone balancing Mel Gorman
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=1403079807-24690-2-git-send-email-mgorman@suse.de \
--to=mgorman@suse.de \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).