From: Rik van Riel <riel@conectiva.com.br>
To: Daniel Phillips <phillips@arcor.de>
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 14:29:26 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0210011426050.653-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <E17wQhL-0005vQ-00@starship>
On Tue, 1 Oct 2002, Daniel Phillips wrote:
> 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.
Every page replacement system has a worst case, 2.5 is closer to
LRU than 2.4 and it's well possible that the randomisation 2.4
does means we don't trigger the worst case here.
I don't know for sure, but I have a feeling that EVERY algorithm
for page replacement can be tricked into performing worse than
random page replacement for some particular workload. It might
even be provable ;)
> > > 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?
No competition ? I know _I_ don't have a machine dedicated to
gimp and I like to be able to continue listening to mp3s while
the gimp is chewing on a large image...
cheers,
Rik
--
A: No.
Q: Should I include quotations after my reply?
http://www.surriel.com/ http://distro.conectiva.com/
next prev parent reply other threads:[~2002-10-01 17:27 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
2002-10-01 17:29 ` Rik van Riel [this message]
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=Pine.LNX.4.44L.0210011426050.653-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=l.allegrucci@tiscalinet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/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).