All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: My end user testing of 2.4.8-ish kernels
Date: Sat, 12 Jan 2002 23:30:27 -0800	[thread overview]
Message-ID: <3C413793.F8F648B5@zip.com.au> (raw)
In-Reply-To: <3C41350D.9070407@pobox.com>

J Sloan wrote:
> 
> I did some testing today on the mini-low-latency patch.
> 
> I must admit that I was totally biased towards it from the start.
> 
> While it certainly didn't hurt anything, the bottom line is that
> after hours of mp3/dbench tests, I was unable to quantify any real
> difference between 2.4.18-pre3 vanilla and with mini low latency.
> They exhibit pretty much the same behaviour in terms of how much
> dbench it takes to start hearing audio dropouts in xmms - they were
> both smooth up to dbench 40, but started exhibiting sporadic audio
> dropouts at dbench 64.

Oh well.   I must have missed one.

> Out of curiosity I booted up 2.4.18pre2-aa2 and found it a real gem.
> To my pleasant suprise I was able to run dbench 128 without hearing
> a _single_ audio dropout. (the dbench 128 result was 19.75 MB/sec)
> 
> With dbench 192 I did start to hear some occasional dropouts, but
> they were generally short, e.g. 100ms or so.
> 
> In any event, all the 2.4.18-pre-ish kernels I tested today are much
> better at this than e.g. 2.4.7 - at least on my hardware, I am now
> getting excellent interactive performance under load without preempt
> or low-latency patches, and that's a good thing.
> 
> IMHO the -aa kernel seems to the clear winner here -
> 

the -aa kernel basically includes everything that's in the mini-ll
patch.  If you merge -aa, you get mini-ll.  Plus the one I missed :)

-

  reply	other threads:[~2002-01-13  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13  7:19 My end user testing of 2.4.8-ish kernels J Sloan
2002-01-13  7:30 ` Andrew Morton [this message]
2002-01-13  7:43   ` J Sloan

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=3C413793.F8F648B5@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=jjs@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.