linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@norran.net>
To: Chris Evans <chris@scary.beasts.org>
Cc: linux-mm@kvack.org
Subject: Re: 2.4.0test9 vm: disappointing streaming i/o under load
Date: Thu, 12 Oct 2000 00:10:11 +0200	[thread overview]
Message-ID: <39E4E543.8A4EB3BF@norran.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0010112154300.23989-100000@ferret.lmh.ox.ac.uk>

Hi,

(you do have DMA enabled...)

I have tested throughput - new kernels are rather good.

I have also tested latency stuff in test9 - I have not
seen any thing as bad as your results.
But my audio apps runs with high priority...

To be able to determine the cause
Try to to renice your audio deamon (and audio clients)
 renice -10 <pid>


Did it become better?


/RogerL


Chris Evans wrote:
> 
> On Wed, 11 Oct 2000, Eric Lowe wrote:
> 
> > > Unfortunately, 2.4.0test9 exhibits poor streaming i/o performance when
> > > under a bit of memory pressure.
> 
> [...]
> 
> > Would you try setting /proc/sys/vm/page-cluster to 8 or 16 and let
> > me know the results?  I think one _part_ of the problem is that
> > when the swapper isn't agressive enough, it causes too much disk
> > thrashing which gets in the way of normal I/O... my experience
> > has been that with modern disks with 512K+ cache you have to
> > write in 64K clusters to get optimum throughput.
> 
> Raising the cluster size didn't seem to do much apart from generally slow
> down interactive response. Lowering it, however, seemed to make playback
> less jittery. I guess that's to be expected; faulting in large chunks of
> sequential i/o won't help much when under memory pressure because the
> pages will get thrown out again before they get a chance to be
> used. Especially with drop_behind.
> 
> Rik what do you think.
> 
> 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/

--
Home page:
  http://www.norran.net/nra02596/
--
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 22:10 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   ` 2.4.0test9 vm: disappointing streaming i/o under load Chris Evans
2000-10-11 11:38     ` Eric Lowe
2000-10-11 20:59       ` Chris Evans
2000-10-11 22:10         ` Roger Larsson [this message]
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=39E4E543.8A4EB3BF@norran.net \
    --to=roger.larsson@norran.net \
    --cc=chris@scary.beasts.org \
    --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