mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul <set@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Benchmarks for performance patches (-ck) for 2.4.19
Date: Mon, 2 Sep 2002 01:22:03 -0400	[thread overview]
Message-ID: <20020902052203.GC2925@squish.home.loc> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209012327360.1857-100000@imladris.surriel.com>

Rik van Riel <riel@conectiva.com.br>, on Sun Sep 01, 2002 [11:32:42 PM] said:
> On Sun, 1 Sep 2002, Ed Sweetman wrote:
> > I mean, besides making the kernel with as low latency as possible, what
> > is bad about the responsiveness in the kernel?  If there's any lag in
> > responsiveness that i see it's always something X related, particularly
> > Xfree86.
> 
> "low latency" != responsiveness
> 
> Any latency which is below the point the user can notice
> is effectively zero, so whether the 10000 wakeups/minute
> that the user doesn't notice are 2ms or 5ms don't really
> matter.
> 
> What does matter are the wakeups that make the user's
> mp3 skip, even if these don't influence the statistics
> at all because there's only 1 every few minutes, or none,
> if the VM is balanced right ;)
> 
> Another responsiveness thing is how fast you can swap in
> Mozilla when the user comes in in the morning. More of a
> throughput than a latency thing in this case ... but you
> still have to make sure the mp3 doesn't skip while mozilla
> is being loaded.
> 
> regards,
> 
> Rik

	Hi;

	I just thought I would toss this in: For some classes
of users, latency is extremely critical. For example, people
making music live, doing realtime audio effects processing, or
recording audio. These people would probably like it below 2ms.
	mp3 playing latency requirements are very
loose-- the buffer takes up the slack, unless the latency is
insane.
	The good news is that for me, using the ck4 patchset,
my smp system is stable, and has a max latency of 3.5ms under
latencytest (during a make -j4 kernel compile no less) _and_
outperformed (slightly) virgin 2.4.19 on generic benchmarks.
(like building a kernel, bonnie,...)	
	Latency may not be the holy grail, but it remains
a valid requirement for a class of user. It may not merit
degredation for the common case, but perhaps it need not?

Paul
set@pobox.com

ps. ck4 uses the aa vm, but if there was a version with rmap,
I would test it.

  parent reply	other threads:[~2002-09-02  5:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  1:10 Con Kolivas
2002-09-02  2:03 ` Ed Sweetman
2002-09-02  2:32   ` Rik van Riel
2002-09-02  4:00     ` Ed Sweetman
2002-09-02  7:39       ` Ingo Oeser
2002-09-02 13:20         ` Rik van Riel
2002-09-03  3:16         ` jw schultz
2002-09-02  5:22     ` Paul [this message]
2002-09-02  5:40       ` J Sloan
2002-09-02  5:57       ` Andrew Morton
2002-09-02  3:24 Dieter Nützel
2002-09-02  3:41 ` Rik van Riel
2002-09-02  3:42 ` Con Kolivas
2002-09-02  4:21   ` Randy.Dunlap
2002-09-02  9:12 Con Kolivas
2002-09-04  3:39 ` Paul
2002-09-02 12:50 Martin Knoblauch
2002-09-04  5:15 Wade

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=20020902052203.GC2925@squish.home.loc \
    --to=set@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®