public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruce Guenter <bruceg@em.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Where's all my memory going?
Date: Thu, 10 Jan 2002 02:45:20 -0600	[thread overview]
Message-ID: <20020110024520.A29045@em.ca> (raw)
In-Reply-To: <E16OMpF-0001pj-00@the-village.bc.nu> <Pine.LNX.4.33L.0201092034590.2985-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0201092034590.2985-100000@imladris.surriel.com>; from riel@conectiva.com.br on Wed, Jan 09, 2002 at 08:36:13PM -0200

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

On Wed, Jan 09, 2002 at 08:36:13PM -0200, Rik van Riel wrote:
> Matt's system seems to go from 900 MB free to about
> 300 MB (free + cache).
> 
> I doubt qmail would eat 600 MB of RAM (it might, I
> just doubt it) so I'm curious where the RAM is going.

I am seeing the same symptoms, with similar use -- ext3 filesystems
running qmail.  Adding up the RSS of all the processes in use gives
about 75MB, while free shows:

             total       used       free     shared    buffers     cached
Mem:        901068     894088       6980          0     157568     113856
-/+ buffers/cache:     622664     278404
Swap:      1028152      10468    1017684

This are fairly consistent numbers.  buffers hovers around 150MB and
cached around 110MB all day.  The server is heavy on write traffic.

> Matt, do you see any suspiciously high numbers in
> /proc/slabinfo ?

What would be suspiciously high?  The four biggest numbers I see are:

inode_cache       139772 204760    480 25589 25595    1
dentry_cache      184024 326550    128 10885 10885    1
buffer_head       166620 220480     96 4487 5512    1
size-64           102388 174876     64 2964 2964    1

I can post complete details for any who wish to investigate further.  I
am not seeing a huge slowdown, but I have no real baseline to compare
against.
-- 
Bruce Guenter <bruceg@em.ca> http://em.ca/~bruceg/ http://untroubled.org/
OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA  2E2A E96F B2DC 6999 80E8

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-01-10  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 17:36 Where's all my memory going? Matt Dainty
2002-01-09 17:47 ` Alan Cox
2002-01-09 22:36   ` Rik van Riel
2002-01-10  8:45     ` Bruce Guenter [this message]
2002-01-10 10:05       ` Andreas Dilger
2002-01-10 11:28         ` Matt Dainty
2002-01-10 14:55         ` Matt Dainty
2002-01-10 16:17           ` David Rees
2002-01-10 20:46           ` Andreas Dilger
2002-01-10 22:24             ` Bruce Guenter
2002-01-10 22:36               ` Andreas Dilger
2002-01-14 11:40                 ` Matt Dainty
2002-01-10 22:18         ` Bruce Guenter
  -- strict thread matches above, loose matches on Subject: below --
2002-01-11 15:30 Rolf Lear

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=20020110024520.A29045@em.ca \
    --to=bruceg@em.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox