From: Jeff Moyer <jmoyer@redhat.com>
To: Ralf Gross <rg@STZ-Softwaretechnik.com>
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: io-scheduler tuning for better read/write ratio
Date: Mon, 22 Jun 2009 15:42:46 -0400 [thread overview]
Message-ID: <x49hby8jbrd.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20090622163113.GD12483@p15145560.pureserver.info> (Ralf Gross's message of "Mon, 22 Jun 2009 18:31:13 +0200")
Ralf Gross <rg@STZ-Softwaretechnik.com> writes:
> Jeff Moyer schrieb:
>> Jeff Moyer <jmoyer@redhat.com> writes:
>>
>> > Ralf Gross <rg@stz-softwaretechnik.com> writes:
>> >
>> >> Casey Dahlin schrieb:
>> >>> On 06/16/2009 02:40 PM, Ralf Gross wrote:
>> >>> > David Newall schrieb:
>> >>> >> Ralf Gross wrote:
>> >>> >>> write throughput is much higher than the read throughput (40 MB/s
>> >>> >>> read, 90 MB/s write).
>> >>> >
>> >>> > Hm, but I get higher read throughput (160-200 MB/s) if I don't write
>> >>> > to the device at the same time.
>> >>> >
>> >>> > Ralf
>> >>>
>> >>> How specifically are you testing? It could depend a lot on the
>> >>> particular access patterns you're using to test.
>> >>
>> >> I did the basic tests with tiobench. The real test is a test backup
>> >> (bacula) with 2 jobs that create 2 30 GB spool files on that device.
>> >> The jobs partially write to the device in parallel. Depending which
>> >> spool file reaches the 30 GB first, one starts reading from that file
>> >> and writing to tape, while to other is still spooling.
>> >
>> > We are missing a lot of details, here. I guess the first thing I'd try
>> > would be bumping up the max_readahead_kb parameter, since I'm guessing
>> > that your backup application isn't driving very deep queue depths. If
>> > that doesn't work, then please provide exact invocations of tiobench
>> > that reprduce the problem or some blktrace output for your real test.
>>
>> Any news, Ralf?
>
> sorry for the delay. atm there are large backups running and using the
> raid device for spooling. So I can't do any tests.
>
> Re. read ahead: I tested different settings from 8Kb to 65Kb, this
> didn't help.
>
> I'll do some more tests when the backups are done (3-4 more days).
The default is 128KB, I believe, so it's strange that you would test
smaller values. ;) I would try something along the lines of 1 or 2 MB.
I'm CCing Fengguang in case he has any suggestions.
Cheers,
Jeff
p.s. Fengguang, the thread starts here:
http://lkml.org/lkml/2009/6/16/390
next prev parent reply other threads:[~2009-06-22 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 15:43 Ralf Gross
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 [this message]
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=x49hby8jbrd.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rg@STZ-Softwaretechnik.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
all inboxes | Powered by JetHome®