All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: About the need of a swap area
Date: Sat, 27 Jul 2002 14:22:20 +0200	[thread overview]
Message-ID: <3D42907C.mailFS15JQVA@viadomus.com> (raw)

    Hi all :))

    I read a time ago that, no matter the RAM you have, adding a
swap-area will improve performance a lot. So I tested.

    I created a swap area twice as large as my RAM size (just an
arbitrary size), that is 1G. I've tested with lower sizes too. My RAM
is never filled (well, I haven't seen it filled, at least) since I
always work on console, no X and things like those. Even compiling
two or three kernels at a time don't consume my RAM. What I try to
explain is that the swap is not really needed in my machine, since
the memory is not prone to be filled.

    Well, I haven't notice any change in performance, and the swap
area is *never* used. That contradicts what I've read about that, no
matter your free RAM size, a bit of swap is always used. That is not
my case, definitely.

    So my question is: should I use a swap-area for improving
performance (or whatever else), or should I use those precious bytes
to improving my porn collection }:))? Seriously: I don't understand
how the swap works, I don't know if the swap area is used only when
RAM is exhausted or when the free RAM goes low beyond some point,
etc... I've read (just took a look) the kernel archives about swap
and it haven't light me O:))

    Thanks a lot :)
    Raúl

             reply	other threads:[~2002-07-27 12:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-27 12:22 DervishD [this message]
2002-07-27 14:42 ` About the need of a swap area Ville Herva
2002-07-27 15:47   ` Rik van Riel
2002-07-27 20:41     ` Buddy Lumpkin
2002-07-27 20:50       ` Rik van Riel
2002-07-27 16:11   ` DervishD
2002-07-27 17:01     ` Ville Herva
2002-07-28 11:04       ` DervishD
2002-07-29 13:14       ` [lkml] " Ian Soboroff
2002-07-28  0:02   ` Denis Vlasenko
2002-07-27 20:58     ` Austin Gonyou
2002-07-27 22:22       ` Buddy Lumpkin
2002-07-27 23:40         ` Alan Cox
2002-07-27 22:35           ` Rik van Riel
2002-07-27 22:49             ` Buddy Lumpkin
2002-07-27 23:36               ` Daniel Phillips
2002-07-27 22:39           ` Buddy Lumpkin
2002-07-28  0:03             ` Alan Cox
2002-07-27 22:52               ` Rik van Riel
2002-07-27 23:01               ` Buddy Lumpkin
2002-07-28  0:28                 ` Alan Cox
2002-07-27 23:34                   ` Buddy Lumpkin
2002-07-28  6:58             ` Ville Herva
2002-07-28  7:59               ` Buddy Lumpkin
2002-07-28  8:19                 ` Ville Herva
2002-07-28 14:11               ` Rik van Riel
2002-07-28 15:57                 ` Ville Herva
2002-07-28 18:48               ` Buddy Lumpkin
2002-07-28 18:58                 ` Ed Sweetman
2002-07-28 19:29                   ` Rik van Riel
2002-07-28 19:47                     ` Ed Sweetman
2002-07-28 20:42                       ` Buddy Lumpkin
2002-07-28 20:27                 ` Ville Herva
2002-07-30 19:31           ` Andy Isaacson
2002-07-28 16:20         ` Austin Gonyou
2002-07-29  7:18 ` Val Henson

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=3D42907C.mailFS15JQVA@viadomus.com \
    --to=raul@pleyades.net \
    --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 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.