From: Andrew Morton <akpm@zip.com.au>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Report: 2.4.18 very high latencies (with lowlat. and pre-empt patches)
Date: Fri, 05 Apr 2002 11:58:16 -0800 [thread overview]
Message-ID: <3CAE01D8.EB75F7A2@zip.com.au> (raw)
In-Reply-To: <E16tEL4-0006fr-00@antoli.gallimedina.net> <3CACD3BC.1EB55BCC@zip.com.au> <E16tQlJ-0007ZV-00@antoli.gallimedina.net>
Ricardo Galli wrote:
>
> 1. Put ten (10) to twenty (20) files of 64-80 MB each in computer B. For
> example in /tmp/test.
>
> 2. Mount in B a disk in A via NFS in, for example, /mnt/A
>
> 3. In B, run the following command:
> cp /tmp/test/* /mnt/A
>
> 4. Check in A how you mouse freezes.
>
You're writing a large amount of data to disk. Presumably
the X server on the same machine wants to read a little
bit of data from the same disk. The X server spends a
long time in disk wait, behind all the writes.
This is somewhat worsened by the VM's tendency to evict
useful pages in favour of less useful pages (cache for
large reads and writes).
You will probably find that the -aa VM will help a little, by
reducing the tendency to evict the wrong pages. You will
probably find that
http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.18-pre1/read-latency2.patch
helps a lot, by allowing the reads to be satisfied more quickly.
You will probably find that current -ac kernels help
a lot, because they contain read-latency2. -ac kernels
also have a different VM which I think makes an attempt
to special-case the large streaming read and write problem.
We're getting there, slowly.
-
prev parent reply other threads:[~2002-04-05 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 21:00 Report: 2.4.18 very high latencies (with lowlat. and pre-empt patches) Ricardo Galli
2002-04-04 22:29 ` Andrew Morton
2002-04-05 10:16 ` Ricardo Galli
2002-04-05 19:45 ` Andrew Morton
2002-04-05 19:58 ` Andrew Morton [this message]
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=3CAE01D8.EB75F7A2@zip.com.au \
--to=akpm@zip.com.au \
--cc=gallir@uib.es \
--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