From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] linux' IO performance sucks
Date: Tue, 4 Jul 2006 21:33:30 -0700 [thread overview]
Message-ID: <7573e9640607042133r763ae763n7f8bb74f76c66600@mail.gmail.com> (raw)
In-Reply-To: <e8fci1$6ui$1@sea.gmane.org>
On 7/4/06, Sven Köhler <skoehler@upb.de> wrote:
> So about every 200MB (i guess the linux box writes the data into the
> cache in the RAM first) linux writes the harddisk. But during that time
> - during the time it writes that 200MB to disk, there is no chance for
> any other IO. I'm playing an mp3 from the very same fileserver. It stops
> playing, because the machine does answer the read-requests.
What filesystem are you using? I've seen this kind of behavior with
XFS, and the anticipatory scheduler, and solved it with the following
in my /etc/conf.d/local.start:
test -f /sys/block/sda/queue/iosched/antic_expire && \
echo 0 >/sys/block/sda/queue/iosched/antic_expire
test -f /proc/sys/vm/laptop_mode && echo 0 >/proc/sys/vm/laptop_mode
test -f /proc/sys/fs/xfs/xfssyncd_centisecs && \
echo 500 > /proc/sys/fs/xfs/xfssyncd_centisecs
You might also play with some of the other settings in
/proc/sys/fs/xfs and see what works for you.
Of course, if you are using a different filesystem or different
scheduler, it might help to know that.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-05 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 3:43 [gentoo-user] linux' IO performance sucks Sven Köhler
2006-07-05 4:31 ` Thomas Cort
2006-07-05 4:33 ` Richard Fish [this message]
2006-07-05 5:45 ` Hemmann, Volker Armin
2006-07-05 10:38 ` Daniel Drake
2006-07-05 10:43 ` Daniel
2006-07-05 21:55 ` Hemmann, Volker Armin
2006-07-05 22:51 ` Daniel Iliev
2006-07-06 0:45 ` Daniel Iliev
2006-07-06 2:01 ` Dale
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=7573e9640607042133r763ae763n7f8bb74f76c66600@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.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