From: David Schwartz <davids@webmaster.com>
To: <ivan@es.usyd.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Memory Leaking. Help!
Date: Mon, 15 Apr 2002 03:00:30 -0700 [thread overview]
Message-ID: <20020415100031.AAA10679@shell.webmaster.com@whenever> (raw)
In-Reply-To: <Pine.LNX.4.33.0204151017480.20961-100000@dipole.es.usyd.edu.au>
>No, I do not. That is why I asked is there a way to find out what is
>eating ram. I am not sure if this a leakage. I am only a paranoid
>sysadmin.
In fact, you have no reason whatsoever to believe the memory is leaking.
It's just being *used*.
>>What does ps -aux imply has all the memory ?
>Top at 9am showed 3.2GB of availabe memory.
>
>Top at 10am showed 2.3Gb of available memory
>
>This top at 11am
>10:19am up 13:23, 6 users, load average: 0.07, 0.03, 0.01
>143 processes: 142 sleeping, 1 running, 0 zombie, 0 stopped
>CPU0 states: 0.0% user, 5.0% system, 0.0% nice, 94.0% idle
>CPU1 states: 0.0% user, 1.0% system, 0.0% nice, 98.0% idle
>Mem: 3799080K av, 2215132K used, 1583948K free, 1580K shrd, 377916K
>buff
>Swap: 8192992K av, 0K used, 8192992K free 1515392K
>cached
If you don't want the memory to be used, take it out of the system and let
it sit on your desk. If you put the memory in the system, the system assumes
that you want to use it. It keeps data in memory that it would otherwise
throw away, that we if it's used again, it doesn't have to be fetched from
disk.
DS
next prev parent reply other threads:[~2002-04-15 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 12:23 Memory Leaking. Help! ivan
2002-04-14 13:15 ` Itai Nahshon
2002-04-14 14:05 ` Alan Cox
2002-04-14 22:51 ` ivan
2002-04-15 0:10 ` Alan Cox
2002-04-15 0:28 ` ivan
2002-04-15 5:18 ` xystrus
2002-04-15 6:10 ` john slee
2002-04-15 9:09 ` Alan Cox
2002-04-15 10:00 ` David Schwartz [this message]
2002-04-15 12:25 ` Eugenio Mastroviti
2002-04-15 15:59 ` Kervin Pierre
2002-04-16 0:36 ` David Schwartz
2002-04-15 11:30 ` Roy Sigurd Karlsbakk
2002-04-15 0:03 ` Tomasz Rola
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=20020415100031.AAA10679@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=ivan@es.usyd.edu.au \
--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