From: Ralf Gross <rg@stz-softwaretechnik.com>
To: linux-kernel@vger.kernel.org
Subject: io-scheduler tuning for better read/write ratio
Date: Tue, 16 Jun 2009 17:43:42 +0200 [thread overview]
Message-ID: <20090616154342.GA7043@p15145560.pureserver.info> (raw)
Hi,
I'm trying to tune the kernel/io-scheduler for better read/write
ratio on a Areca RAID0 device (4 disks, kernel 2.6.26, xfs fs).
I can get 200 MB/s seq. writes and about the same for seq. reads. My
problem is that if there are reads _and_ writes on this device, the
write throughput is much higher than the read throughput (40 MB/s
read, 90 MB/s write).
The deadline scheduler sounded like the way to go for getting better
read results, but reagardless which parameter I change, the ratio keeps
the same.
cfq, noop.. different paramter settings, but alway the same result.
short: is there a way to tune the kernel/scheduler settings in a way
to get a higher read throughput? Writes are not that important,
basicially there are only two 30 GB files on the device/filesystem
that are used to spool data for two LTO-4 tape drives. So I need a
certain read speed to keep both drives streaming. While the data gets
written to one file, I need at least 50 MB/s for reading from the
other file and sent to the tape drive.
Thanks, Ralf
next reply other threads:[~2009-06-16 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 15:43 Ralf Gross [this message]
2009-06-16 16:41 ` David Newall
2009-06-16 18:40 ` Ralf Gross
2009-06-16 18:43 ` Casey Dahlin
2009-06-16 18:56 ` Ralf Gross
2009-06-16 20:16 ` Jeff Moyer
2009-06-22 14:43 ` Jeff Moyer
2009-06-22 16:31 ` Ralf Gross
2009-06-22 19:42 ` Jeff Moyer
2009-06-23 7:24 ` Ralf Gross
2009-06-23 13:53 ` Jeff Moyer
2009-06-24 7:25 ` Ralf Gross
2009-06-24 7:57 ` Al Boldi
2009-06-25 7:26 ` Ralf Gross
2009-06-25 13:45 ` Al Boldi
2009-06-25 7:27 ` Ralf Gross
2009-06-26 2:19 ` Wu Fengguang
2009-06-26 10:44 ` Jens Axboe
2009-06-27 3:46 ` Wu Fengguang
2009-06-29 9:47 ` Ralf Gross
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=20090616154342.GA7043@p15145560.pureserver.info \
--to=rg@stz-softwaretechnik.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®