public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Knight <nknight@pocketinet.com>
To: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>, christian e <cej@ti.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: minimizing swap usage
Date: Tue, 25 Dec 2001 03:02:05 -0800	[thread overview]
Message-ID: <WHITEp4nbukgQu0216A000005b2@white.pocketinet.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112200559350.8883-100000@shell1.aracnet.com>
In-Reply-To: <Pine.LNX.4.33.0112200559350.8883-100000@shell1.aracnet.com>

On Thursday 20 December 2001 06:05 am, M. Edward (Ed) Borasky wrote:
> On Thu, 20 Dec 2001, christian e wrote:
> > Hi,all
> >
> > Can someone give me a pointer to how I can avoid somethign like
> > this:
> >
> > foo@bar]$ free -m
> > 	    total       used       free     shared    buffers     cached
> > Mem:           249        245          4          0          6     
> >  136 -/+ buffers/cache:        102        147
> > Swap:          243         89        153
> >
> > What's with all the caching when my apps crawl because it's
> > swapping so much ? I've tried to adjust /proc/vm/kswapd parameters
> > but that doesn't seem to help..I'd like to postpone the swapping
> > until its almost out of physical memory..
>
> This may seem counterintuitive, but postponing swapping / cache
> flushing to disk till the last possible moment is counterproductive.
> It's a little like procrastination in the time management world --

Why not add a config option to choose between code for two behaviors:
(1 being the default, of course)
1. Current behavior, usualy a Good Thing, sometimes a Bad Thing, I've 
had apps that had to call up in their entirety from swap space, while I 
still had plenty of "avalible" RAM left ("avalible" meaning free, and 
cache/buffers.) It seems the kernel puts a higher priority on caching 
and buffers than on memory that hasn't been accessed in a while, which, 
as I said, is usualy good, but not always.

2. Don't swap ANYTHING to disk until avalible RAM drops below, say, 
15%. And put cache on a sanity check; if the system is going to swap to 
disk because avalible RAM drops below 15%, and  cache makes up more 
than, say, 45%, start dropping the oldest stuff in the cache to free up 
RAM instead of swapping. (I'm assuming 128-256MB+ of RAM here, for 
anything smaller, default is probably best.)

At the very least, I'd like to see #2 tried, if someone that knows the 
VM system has time to spare on it.
Cache/swap practices in the kernel have been bugging me for a long time.

  reply	other threads:[~2001-12-25 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 13:30 minimizing swap usage christian e
2001-12-20 14:05 ` M. Edward (Ed) Borasky
2001-12-25 11:02   ` Nicholas Knight [this message]
     [not found]     ` <01122513421800.02101@manta>
2001-12-25 11:50       ` Nicholas Knight
     [not found]   ` <3C2B0A5A.4070101@ti.com>
     [not found]     ` <01122714150100.12566@manta>
2001-12-28  3:52       ` Nicholas Knight

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=WHITEp4nbukgQu0216A000005b2@white.pocketinet.com \
    --to=nknight@pocketinet.com \
    --cc=cej@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=znmeb@aracnet.com \
    /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