From: Andrew Morton <akpm@zip.com.au>
To: Jim Wilcoxson <jim@rubylane.com>
Cc: linux-mm@kvack.org
Subject: Re: 2.2.20 suspends everything then recovers during heavy I/O
Date: Thu, 04 Apr 2002 21:29:22 -0800 [thread overview]
Message-ID: <3CAD3632.E14560B@zip.com.au> (raw)
In-Reply-To: <4.2.0.58.20020404140237.00b6c390@london.rubylane.com>
Jim Wilcoxson wrote:
>
> I'm setting up a new system with 2.2.20, Ingo's raid patches, plus
> Hedrick's IDE patches.
>
> When doing heavy I/O, like copying partitions between drives using tar in a
> pipeline, I've noticed that things will just stop for long periods of time,
> presumably while buffers are written out to the destination disk. The
> destination drive light is on and the system is not exactly hung, because I
> can switch consoles and stuff, but a running vmstat totally suspends for
> 10-15 seconds.
>
> Any tips or patches that will avoid this? If our server hangs for 15
> seconds, we're going to have tons of web requests piled up for it when it
> decides to wakeup...
>
Which filesystem are you using?
First thing to do is to ensure that your disks are achieving
the expected bandwidth. Measure them with `hdparm -t'.
If the throughput is poor, and they're IDE, check the
chipset tuning options in your kernel config and/or
tune the disks with hdparm.
If all that fails, you can probably smooth things
out by tuning the writeback parameters in /proc/sys/vm/bdflush
(if that's there in 2.2. It's certainly somewhere :))
Set the `interval' value smaller than the default five
seconds, set `nfract' higher. Set `age_buffer' lower..
And finally: don't go copying entire partitions around
on a live web server :)
-
--
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/
next prev parent reply other threads:[~2002-04-05 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 22:06 Jim Wilcoxson
2002-04-05 5:29 ` Andrew Morton [this message]
2002-04-05 18:27 ` jim
2002-04-05 18:47 ` Martin J. Bligh
2002-04-05 19:52 ` jim
2002-04-05 19:55 ` jim
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=3CAD3632.E14560B@zip.com.au \
--to=akpm@zip.com.au \
--cc=jim@rubylane.com \
--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