public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: how to use RAM
Date: Tue, 13 Oct 2009 00:52:58 +0300	[thread overview]
Message-ID: <hb08fn$rv3$1@ger.gmane.org> (raw)
In-Reply-To: <4AD3953C.5030706@xunil.at>

On 10/12/2009 11:44 PM, Stefan G. Weichinger wrote:
>
> Greets, gentoo-users,
>
> as I ordered myself an upgrade from 4 to 8 gigs of RAM for my main
> workstation, just because it's rather cheap now and I have good use for
> the "old" 4 gigs I wonder what to do with those shiny new additional 4 gigs.
>
> OK, linux uses it for IO-caching, yep ...
>
> I have some ram-disk already for compiling stuff (portage-stuff) and I
> can think of increasing app-caches like operas own ram-cache to make use
> of the memory.
>
> I will give my virtual machines more RAM to improve their performance,
> yes, this is maybe the main reason for me to upgrade RAM.
>
> But are there any other things I might forget?
>
> Are there any creative non-ricer ways to really make use of it?
>
> I would like to hear your opinion on this, I am quite sure the
> gentoo-community knows one trick or the other ;-)

One thing I did after my RAM upgrade was to put:

   vm.swappiness = 30

in /etc/sysctl.conf to make the kernel use less swap.  (The default 
swappiness is 60.)  Don't use values lower than 20 though, and better 
don't disable swap completely; it's marginal, but complete absence of 
swap can hurt performance even with plenty of RAM.




  reply	other threads:[~2009-10-12 21:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 20:44 [gentoo-user] how to use RAM Stefan G. Weichinger
2009-10-12 21:52 ` Nikos Chantziaras [this message]
2009-10-12 22:01   ` [gentoo-user] " Stefan G. Weichinger
2009-10-12 22:09 ` [gentoo-user] " KH
2009-10-12 22:39   ` Alan McKinnon
2009-10-13 11:35     ` Stefan G. Weichinger
2009-10-12 22:45   ` Dale
2009-10-13  5:56     ` KH
2009-10-13 16:26 ` Joshua Murphy
2009-10-13 17:58   ` Stefan G. Weichinger
2009-10-14  0:03     ` Joshua Murphy
2009-10-14  7:18       ` Stefan G. Weichinger
2009-10-14  9:42         ` KH
2009-10-14 10:08           ` Stefan G. Weichinger
2009-10-14 10:25           ` Dale
2009-10-14 11:31             ` pk
2009-10-14 11:36               ` Alan McKinnon
2009-10-14 14:33               ` KH
2009-10-14 15:04                 ` Dale
2009-10-14 16:55                   ` Stefan G. Weichinger
2009-10-14 19:59                     ` Alan McKinnon
2009-10-14 20:31                       ` Stefan G. Weichinger
2009-10-14 20:21                     ` Volker Armin Hemmann
2009-10-14 20:28                       ` Stefan G. Weichinger
2009-10-14 20:38                         ` Volker Armin Hemmann
2009-10-14 20:43                           ` Stefan G. Weichinger
2009-10-14 20:34                       ` Alan McKinnon
2009-10-14 20:40                         ` Volker Armin Hemmann
2009-10-14 20:40                         ` Stefan G. Weichinger
2009-10-14 20:57                           ` Alan McKinnon
2009-10-14 20:48                         ` Neil Bothwick
2009-10-14 21:01                           ` Alan McKinnon
2009-10-15  1:24                         ` Stroller

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='hb08fn$rv3$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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