All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Bryant <raybry@sgi.com>
To: John Bradford <john@grabjohn.com>
Cc: Silviu Marin-Caea <silviu@genesys.ro>, linux-kernel@vger.kernel.org
Subject: Re: dynamic allocation of swap disk space
Date: Tue, 11 May 2004 11:28:25 -0500	[thread overview]
Message-ID: <40A0FF29.1060006@sgi.com> (raw)
In-Reply-To: <200405111552.i4BFqFMN000112@81-2-122-30.bradfords.org.uk>

Hi John,

John Bradford wrote:
>
> 
> Not necessarily.  Increasing swap can allow more physical RAM to be used for
> caching data from disk.
> 
> Imagine a system with limited physical RAM, and limited swap space, running a
> process which causes a lot of filesystem activity on the same physical disk
> as is being used for swap.  If the total RAM, both physical and swap is almost
> completely full, increasing the swap space may allow some data from physical
> RAM to be swapped out, in favour of caching filesystem data from the disk.

Hmmm... Lets see, we have a program (or set of programs) in memory that is 
thrashing, i. e. it is page faulting at a rate that is higher than the vm 
system can supply pages, so it is spending its time waiting for pages and the 
disk subsystem is busy.  Now, if we increase the amount of data cached from 
disk, without increasing main memory, we've decreased the amount of memory 
available to the thrashing program, perhaps making its problems worse?

Well, I guess all this shows is that with the vm subsystem, speculation is 
often useless, one has to fire up the box with a carefully constructed 
workload and see what happens.

> 
> Without knowing more details of the original poster's machine, it's difficult
> to give specific advice about how to solve the problem.
>

I certainly agree with that.  Time for this thread to die, I think.  :-)

Cheers.

> John.
> 

-- 
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
raybry@sgi.com             raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------


  parent reply	other threads:[~2004-05-11 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.n6pggn5.84en31@ifi.uio.no>
2004-05-11 15:22 ` dynamic allocation of swap disk space Ray Bryant
2004-05-11 15:52   ` John Bradford
2004-05-11 15:54     ` Valdis.Kletnieks
2004-05-11 16:39       ` John Bradford
2004-05-11 16:28     ` Ray Bryant [this message]
2004-05-12  6:56     ` Silviu Marin-Caea
2004-05-11 16:00   ` Oliver Neukum
2004-05-10  8:50 Silviu Marin-Caea
2004-05-10 10:03 ` John Bradford
2004-05-10 10:22   ` Silviu Marin-Caea
2004-05-10 20:28     ` Paul Jackson

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=40A0FF29.1060006@sgi.com \
    --to=raybry@sgi.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=silviu@genesys.ro \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.