public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:45:18 -0800	[thread overview]
Message-ID: <3CADFECE.F2A6374@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:
> 
> To test computer A, which has installed Linux 2.4.18 + all low latency
> patches.
> 
> 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 ton of data to disk, and this causes the X
server to have long freezes.

Probably the X server is waiting on a disk read, which is
blocked behind all the writes.  This is worsened by the
VM's tendency to evict useful data in favour of caching
large read/write data.

You'll find that the -aa VM will improve the page replacement
decisions, so the X server won't have to read random
pages as often.  This should help a bit.  The patch at
http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.18-pre1/read-latency2.patch
will decrease the time which the remaining reads take.
This should help a lot.

We're getting there, albeit a bit slowly.

-

  reply	other threads:[~2002-04-05 19:47 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 [this message]
2002-04-05 19:58     ` Andrew Morton

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=3CADFECE.F2A6374@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