linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <akpm@digeo.com>,
	Lorenzo Allegrucci <l.allegrucci@tiscalinet.it>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: qsbench, interesting results
Date: Tue, 1 Oct 2002 19:20:39 +0200	[thread overview]
Message-ID: <E17wQhL-0005vQ-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210011407480.653-100000@duckman.distro.conectiva>

On Tuesday 01 October 2002 19:13, Rik van Riel wrote:
> With one process that needs 150% of RAM as its working set,
> there simply is no way to win.

True, the object is merely to suck as little as possible.  Note that
2.4.xx trounces 2.5.xx rather soundly on the test in question.
 
> > It should run the process as efficiently as possible, given that there
> > isn't any competition.
> 
> If there is no competition I agree.  However, if the system has
> something else running at the same time as qsbench I think the
> system should make an effort to have _only_ qsbench thrashing
> and not every other process in the system as well.

Did I miss something?  I thought the test was just a single instance
of qsbench.

> > Try loading a high res photo in gimp and running any kind of interesting
> > script-fu on it.  If it doesn't thrash, boot with half the memory and
> > repeat.
> 
> But, should just the gimp thrash, or should every process on the
> machine thrash ?

Gimp should thrash exactly as much as it needs to, to get its job
done.  No competition, remember?  I realize you're getting ready to
do a sales job for process load control, but you needn't bother, I'm
already sold.  We're not talking about that.

-- 
Daniel

  reply	other threads:[~2002-10-01 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 14:15 qsbench, interesting results Lorenzo Allegrucci
2002-09-29 16:26 ` bert hubert
2002-09-29 19:56   ` Lorenzo Allegrucci
2002-09-29 20:00     ` bert hubert
2002-09-29 21:05       ` Lorenzo Allegrucci
2002-09-30  5:57 ` Andrew Morton
2002-10-01 14:05   ` Daniel Phillips
2002-10-01 16:52     ` Rik van Riel
2002-10-01 17:03       ` Daniel Phillips
2002-10-01 17:13         ` Rik van Riel
2002-10-01 17:20           ` Daniel Phillips [this message]
2002-10-01 17:29             ` Rik van Riel
2002-10-01 17:38               ` Daniel Phillips
2002-10-01 18:18         ` Lorenzo Allegrucci
2002-10-01 17:15       ` Larry McVoy
2002-10-01 18:04     ` Andrew Morton
2002-10-01 18:20       ` Rik van Riel
2002-10-01 18:35       ` Daniel Phillips

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=E17wQhL-0005vQ-00@starship \
    --to=phillips@arcor.de \
    --cc=akpm@digeo.com \
    --cc=l.allegrucci@tiscalinet.it \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).