mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M. Edward Borasky" <znmeb@aracnet.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Which is better at vm, and why? 2.2 or 2.4
Date: Sat, 13 Oct 2001 11:37:22 -0700	[thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBCEOLDOAA.znmeb@aracnet.com> (raw)
In-Reply-To: <20011013141709.L249@localhost>

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Patrick
> McFarland
> Sent: Saturday, October 13, 2001 11:17 AM
> To: M. Edward Borasky
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Which is better at vm, and why? 2.2 or 2.4
>
>
> Hmm, I see that as very bad. There should be a bunch of sysctls
> to do that easily. Also, I heard that 2.4 (and I'm assuming 2.2
> as well) swaps pages on a last-used-age basis, instead of either
> a number-of-times-used or a hybrid of the two. That kinda seems
> stupid, especially if you get a bunch of apps running that just
> cycle thru pages, instead of the most used pages staying in
> memory, and the least used being swapped back and forth with
> about 2 or 3 megs of memory used to store the least used pages in memory

What do you see as bad? The ability to change tuning parameters on the fly
or the lack of such ability? At the very least, I need to be able to poke
settings with a debugger, and a more systematic and user-friendly interface
would be preferable.

Your example is exactly what I'm talking about! Neither the applications nor
the kernel are "stupid"; they are doing exactly what they're being paid to
do. My job as a system tuner is to make sure that the users get the response
times and throughputs they need, given the inherent limits of how much they
can afford to pay for processors, memory and disk. As an aside, I also need
to be able to figure out what those limits are -- when it's time to add
capacity rather than just tune the system.
--
M. Edward (Ed) Borasky, Chief Scientist, Borasky Research
http://www.borasky-research.net
mailto:znmeb@borasky-research.net
http://groups.yahoo.com/group/BoraskyResearchJournal

Q: How do you tell when a pineapple is ready to eat?
A: It picks up its knife and fork.


  parent reply	other threads:[~2001-10-13 18:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 17:02 Patrick McFarland
2001-10-13 17:16 ` Alan Cox
2001-10-13 18:06   ` M. Edward Borasky
2001-10-13 18:17     ` Patrick McFarland
2001-10-13 18:29       ` Rik van Riel
2001-10-13 18:42         ` Patrick McFarland
2001-10-13 18:53           ` Patrick McFarland
2001-10-13 18:58             ` Rik van Riel
2001-10-13 19:04               ` Patrick McFarland
2001-10-13 19:10                 ` Rik van Riel
2001-10-13 19:28             ` Wilson
2001-10-13 20:12               ` [solid]
2001-10-13 20:21               ` Patrick McFarland
2001-10-13 19:17           ` Rik van Riel
2001-10-13 18:37       ` M. Edward Borasky [this message]
2001-10-20  0:38     ` Daniel Phillips
2001-10-20  1:05     ` Robert Love
2001-10-20 19:56       ` Mike Fedyk
2001-10-20 20:03       ` Robert Love
2001-10-13 17:48 ` Mark Hahn
2001-10-13 21:29   ` Mike Fedyk
2001-10-13 21:47     ` Mark Hahn
     [not found] <20011013132327.F249@localhost>
     [not found] ` <E15sSey-0003Jf-00@the-village.bc.nu>
2001-10-13 17:33   ` Patrick McFarland
     [not found]     ` <E15sSti-0003ME-00@the-village.bc.nu>
2001-10-13 17:49       ` Patrick McFarland

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=HBEHIIBBKKNOBLMPKCBBCEOLDOAA.znmeb@aracnet.com \
    --to=znmeb@aracnet.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®