linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chris Evans <chris@scary.beasts.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: 2.4.0test9 vm: disappointing streaming i/o under load
Date: Wed, 11 Oct 2000 01:06:11 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0010110056230.7853-100000@ferret.lmh.ox.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0010101738110.11122-100000@duckman.distro.conectiva>

Hi,

Finally got round to checking out 2.4.0test9.

Unfortunately, 2.4.0test9 exhibits poor streaming i/o performance when
under a bit of memory pressure.

The test is this: boot with mem=32M, log onto GNOME and start xmms playing
a big .wav ripped from a CD (this requires 100-200k read i/o per second).

Then, I start then kill netscape. I then started a find / and started
gnumeric firing up at the same time.

Results
=======

2.2 RH7.0: the music skipped maybe twice briefly during the test.

2.4.0test9: music stuttered repeatedly while netscape started. Worse, when
firing up gnumeric with the find / on the go, there were big pauses in
sound output. On pause was over 5 seconds!!!


So not so hot.

Could this perhaps be related to the drop_behind magic penalizing
streaming i/o pages too much? Perhaps the greater ago on the i/o pages
means that when there is a little memory pressure, they are getting thrown
out the page cache before the app (xmms) gets a chance to use them!

Might it be useful for me to try pre10-1, I note it has more "balancing
fixes".

Cheers
Chris


--
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.eu.org/Linux-MM/

  reply	other threads:[~2000-10-11  0:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200010090419.e994JQT09775@trampoline.thunk.org>
2000-10-10 20:53 ` Updated 2.4 TODO List Rik van Riel
2000-10-11  0:06   ` Chris Evans [this message]
2000-10-11 11:38     ` 2.4.0test9 vm: disappointing streaming i/o under load Eric Lowe
2000-10-11 20:59       ` Chris Evans
2000-10-11 22:10         ` Roger Larsson
2000-10-11 22:46           ` Chris Evans
2000-10-13 16:57             ` Rik van Riel
2000-10-11 18:38   ` Updated 2.4 TODO List tytso
2000-10-11 23:52     ` [RFC] atomic pte updates for x86 smp Ben LaHaise
2000-10-12  0:09       ` Linus Torvalds
2000-10-12  4:03         ` Benjamin C.R. LaHaise
2000-10-12  4:06           ` David S. Miller
2000-10-12  4:31             ` Cort Dougan
2000-10-12  4:37             ` Benjamin C.R. LaHaise
2000-10-12  6:42           ` Linus Torvalds
2000-10-12  8:13             ` Ingo Molnar
2000-10-12  8:56               ` David S. Miller
2000-10-12 10:05                 ` Ingo Molnar
2000-10-12 11:10                   ` Ingo Molnar
2000-10-12 15:10             ` Benjamin C.R. LaHaise

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=Pine.LNX.4.21.0010110056230.7853-100000@ferret.lmh.ox.ac.uk \
    --to=chris@scary.beasts.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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