public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Simon Windsor <simon.windsor@cornfield.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: More memory?
Date: Sun, 05 Dec 2004 00:27:54 +0000	[thread overview]
Message-ID: <1102206474.4421.34.camel@gaul.cornfield.org.uk> (raw)
In-Reply-To: <cor8c2$pgv$1@sea.gmane.org>

Hi

SWAP is not necessarily a bad thing. It is mealy a simple way of moving
unused code from memory so that it can be better used, ie disk caching.

Swap can be bad if you have insufficient memory to run your processes.

If your system has lots of disk activity, the OS will assign memory to
cache the disk. This may where you memory is going.

You say that your system is using perl. What else? Apache? MySQL/PgSQL?
etc ...

Please more info ..

All the best

Simon

On Fri, 2004-12-03 at 20:45 -0600, Gabriel M. Beddingfield wrote:
> Grant wrote:
> 
> >> If you don't want it to swap try 'man swapoff' and 'man fstab'
> > 
> > It seems like swap is there for a reason so I don't want to disable
> > it.  What I do want to be able to do is run my system in a manner that
> [snip]
> 
> Just turn it off.  You don't need it unless you run out of RAM.  Swap is
> just for "virtual RAM."  You don't *need* virtual RAM unless you run out of
> physical RAM.
> 
> You may still need 2GB RAM in the future... but turning off swap won't hurt
> anything.  Using 'swapoff' and 'swapon' will let you try-before-you-buy. 
> Editing fstab (comment out the line with the swap partition) will make it
> so for every boot-up.
> 
> What happens when you run out of RAM?  The application doesn't start up.  It
> doesn't crash the system.  Once when attempting a Gentoo install on a 486 I
> ran out of memory when using tar.  I didn't crash, it just didn't untar my
> file.  I turned on swap, and everything worked just fine.
> 
-- 
Simon Windsor

Eml: simon.windsor@cornfield.org.uk
Tel: 01454 617689
Mob: 07960 321599


--
gentoo-user@gentoo.org mailing list


  parent reply	other threads:[~2004-12-05  0:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49bf44f104120306566d7e95cc@mail.gmail.com>
     [not found] ` <1102117306.10326.3.camel@sf.rout.dyndns.org>
     [not found]   ` <49bf44f10412031709175d496@mail.gmail.com>
     [not found]     ` <20041204013213.GA30529@vicerveza.homeunix.net>
     [not found]       ` <49bf44f104120318296c48f892@mail.gmail.com>
2004-12-04 23:49         ` [gentoo-user] More memory? James Colannino
     [not found]         ` <200412040853.22010.uwix@iway.na>
     [not found]           ` <49bf44f104120410162d888ca2@mail.gmail.com>
     [not found]             ` <41B2059F.2010407@pnpitalia.it>
     [not found]               ` <49bf44f10412041057329eda1d@mail.gmail.com>
2004-12-05  1:33                 ` Bastian Balthazar Bux
2004-12-06 16:16           ` Grant
2004-12-06 17:20             ` Jerry McBride
2004-12-06 17:32             ` Billy
2004-12-06 20:36             ` Uwe Thiem
     [not found]     ` <cor8c2$pgv$1@sea.gmane.org>
2004-12-05  0:27       ` Simon Windsor [this message]
2004-12-05  1:39         ` [gentoo-user] " Grant
2004-12-05 12:21           ` Tim Igoe
2004-12-05 18:05             ` Grant

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=1102206474.4421.34.camel@gaul.cornfield.org.uk \
    --to=simon.windsor@cornfield.org.uk \
    --cc=gentoo-user@lists.gentoo.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