public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Iliev <danny@ilievnet.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re:  [OT] AGPART [SOLVED] DRIFT: RAM USAGE
Date: Sun, 6 May 2007 11:34:42 +0300	[thread overview]
Message-ID: <20070506083444.279A29148B@mail.ilievnet.com> (raw)
In-Reply-To: <pan.2007.05.05.09.15.40@cox.net>

On Sat, 5 May 2007 09:15:41 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
--snip--
> 
> Actually, here, I have 8 gigs.  That's a bit overkill.  I'd probably 
> stick with four if I were doing it over, as over four gigs remains 
> entirely empty, most of the time, not even used for cache.
--snip--

In case you didn't know...

There are several kernel configuration options you can tweak to make it
cache more aggressively. Also you could try XFS - it is known to be one
of the most hungry-for-RAM file systems. Please, have in mind that
these tweaks could be dangerous for your file system in case of power
failure. Consider using an UPS.

So, you could try changing the values of the following params
in /etc/sysctl.conf and activate their new values by "sysctl -p"

vm.overcommit_memory 
fs.xfs.xfsbufd_centisecs
fs.xfs.xfssyncd_centisecs 
fs.xfs.age_buffer_centisecs 
vm.dirty_ratio 
vm.dirty_background_ratio
vm.dirty_expire_centisecs
vm.dirty_writeback_centisecs
vm.swappiness 
vm.swap_token_timeout 
vm.vfs_cache_pressure 
vm.page-cluster

The  meanings of these options are described in the kernel docs, so the
files containing the info could be found by grepping like:
"grep -rinm1 dirty_expire_centisecs /usr/src/linux/Documentation". 

Have fun! ;-)

-- 
Best regards,
Daniel

-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2007-05-06  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 17:00 [gentoo-amd64] [OT] AGPART Daniel Iliev
2007-05-04 17:36 ` Jeffrey Gardner
2007-05-04 18:21   ` Wil Reichert
2007-05-04 18:47     ` Jeffrey Gardner
2007-05-05  1:58   ` [gentoo-amd64] " Duncan
2007-05-05  7:58 ` [gentoo-amd64] [OT] AGPART [SOLVED] Daniel Iliev
2007-05-05  9:15   ` [gentoo-amd64] " Duncan
2007-05-05  9:49     ` Peter Humphrey
2007-05-05 13:56     ` Boyd Stephen Smith Jr.
2007-05-06 14:36       ` [gentoo-amd64] Memory usage Was: " Duncan
2007-05-06  8:34     ` Daniel Iliev [this message]
2007-05-06 13:36       ` [gentoo-amd64] Re: [OT] AGPART [SOLVED] DRIFT: RAM USAGE Duncan

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=20070506083444.279A29148B@mail.ilievnet.com \
    --to=danny@ilievnet.com \
    --cc=gentoo-amd64@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