public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Con Kolivas <conman@kolivas.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Benchmarks for performance patches (-ck) for 2.4.19
Date: Sun, 01 Sep 2002 22:03:37 -0400	[thread overview]
Message-ID: <3D72C6F9.6000302@wmich.edu> (raw)
In-Reply-To: 1030929021.3d72ba7dadbe7@kolivas.net

Wouldn't the majority (to an undeniable extent) of the "responsiveness" 
of desktop usage be on X's code? if we are talking about that.  The 
problem with finding a benchmark is that first you have to have a 
definition of what you're benchmarking.  The "system responsiveness" 
term is far too vague. When there's a definition to the term there can 
be a benchmark made to measure it. 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.

You can't really benchmark something where everyone's issues are "things 
go slow when i use "some" benchmark and try using my computer at the 
same time" or "it feels better or worse."   I'd be quite interested in 
making a benchmark and/or using it to help responsiveness in linux, who 
wouldn't want that?  But I just think we have a fairly good kernel and 
the bottleneck is not it in the case of the majority of users and what 
they report as "system responsiveness."  As computers get faster and 
faster we expect to see that reflected in the software we use, perhaps 
it's just making some design issues with X more apparent ...perhaps not. 
  Just some food for thought.




Con Kolivas wrote:
> My merged patchset (http://kernel.kolivas.net) was designed to improve system
> responsiveness. I have yet to find a good benchmark that measures such a thing.
> However, in response to criticism about not providing benchmarks I have made
> available some standard benchmarks at the excellent resources of the open source
> development laboratory scalable test platform. They are available here:
> 
> http://www.osdl.org/stp
> 
> my patchsets are the following:
> -ck5 patch is patch #781
> -ck5-rmap is #782
> -ck5-ll is #783
> 
> I have conducted some basic tests on #781 and the numbers show it is at least
> equivalent to stock 2.4.19 (#747), although as I said none of these benchmarks
> are designed to test desktop system responsiveness.
> 
> Please feel free to conduct any tests you like on these patches. I would be
> interested to hear if anyone can suggest the most suitable benchmark. Please cc
> me to ensure I receive any comments.
> 
> Con Kolivas
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 




  reply	other threads:[~2002-09-02  1:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  1:10 Benchmarks for performance patches (-ck) for 2.4.19 Con Kolivas
2002-09-02  2:03 ` Ed Sweetman [this message]
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
2002-09-02  5:40       ` J Sloan
2002-09-02  5:57       ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
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=3D72C6F9.6000302@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=conman@kolivas.net \
    --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