mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@redhat.com>
To: "Márcio Oliveira" <moliveira@latinsourcetech.com>
Cc: Neil Horman <nhorman@redhat.com>,
	arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Memory Management
Date: Fri, 22 Jul 2005 10:02:27 -0400	[thread overview]
Message-ID: <20050722140227.GA15660@hmsendeavour.rdu.redhat.com> (raw)
In-Reply-To: <42DFA5E6.1080302@latinsourcetech.com>

On Thu, Jul 21, 2005 at 10:40:54AM -0300, Márcio Oliveira wrote:
> 
> >http://people.redhat.com/nhorman/papers/rhel3_vm.pdf
> >I wrote this with norm awhile back.  It may help you out.
> >Regards
> >Neil
> > 
> >
> Neil,
> 
>   Thanks.~10-12GB of total RAM (16GB) are
> 
>   How can Proc virtual memory parameters like inactive_clean_percent, 
> overcommit_memory, overcommit_ratio and page_cache help me to solve / 
> reduce Out Of Memory conditions on servers with 16GB RAM and lots of GB 
> swap?
> 
I wouldn't touch memory overcommit if you are already seeing out of memory
issues.  If you are using lots of pagecache, I would suggest increasing
inactive_clean percent, reducing the pagecahce.max value, and modifying the
bdflush parameters in the above document such that bdflush runs sooner, more
often, and does more work per iteration.  This will help you move data in
pagecache back to disk more aggressively so that memory will be available for
other purposes, like heap allocations. Also if you're using a Red Hat kernel and
you have 16GB of ram in your system, you're a good candidate for the hugemem
kernel.  Rather than a straightforward out of memory condition, you may be
seeing a exhaustion of your kernels address space (check LowFree in
/proc/meminfo).  In this even the hugemem kernel will help you in that it
increases your Low Memory address space from 1GB to 4GB, preventing some OOM
conditions.


>   Kernel does not free cached memory (~10-12GB of total RAM - 16GB). Is 
> there some way to force the kernel to free cached memory?
> 
Cached memory is freed on demand.  Just because its listed under the cached line
below doesn't mean it can't be freed and used for another purpose.  Implement
the tunings above, and your situation should improve.

Regards
Neil

> /proc/meminfo:
> 
>              total:    used:    free:  shared: buffers:  cached:
> Mem:    16603488256 16523333632 80154624        0 70651904 13194563584
> Swap:   17174257664 11771904 17162485760
> MemTotal:     16214344 kB
> MemFree:         78276 kB
> Buffers:         68996 kB
> Cached:       12874808 kB
> 
> Thanks to all.
> 
> Marcio.
> 
> 

-- 
/***************************************************
 *Neil Horman
 *Software Engineer
 *Red Hat, Inc.
 *nhorman@redhat.com
 *gpg keyid: 1024D / 0x92A74FA1
 *http://pgp.mit.edu
 ***************************************************/

  reply	other threads:[~2005-07-22 14:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 12:34 Márcio Oliveira
2005-07-21 13:11 ` Neil Horman
2005-07-21 13:40   ` Márcio Oliveira
2005-07-22 14:02     ` Neil Horman [this message]
2005-07-22 14:32       ` Márcio Oliveira
2005-07-22 19:08         ` Neil Horman
2005-07-22 19:41           ` Márcio Oliveira
2005-07-22 20:58             ` Roger Heflin
2005-07-22 23:23               ` Márcio Oliveira
2005-07-23 18:45                 ` Neil Horman
2005-07-23 23:16                   ` Márcio Oliveira
2005-07-24 18:54                     ` Neil Horman
2005-07-25  1:40                       ` Márcio Oliveira
2005-07-25  9:47                         ` Seiji Kihara
2005-07-25 14:30                         ` Neil Horman
2005-07-25 17:04                           ` Márcio Oliveira
  -- strict thread matches above, loose matches on Subject: below --
2005-07-20 13:10 Memoy Management Márcio Oliveira
2005-07-20 13:24 ` Arjan van de Ven
2005-07-20 14:23   ` Memory Management Márcio Oliveira
2005-07-20 14:37     ` Arjan van de Ven

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=20050722140227.GA15660@hmsendeavour.rdu.redhat.com \
    --to=nhorman@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moliveira@latinsourcetech.com \
    /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

Powered by JetHome