From: Owen Ford <oford@arghblech.com>
To: newbie <linux-newbie@vger.kernel.org>
Subject: Re: Heavy load of graphics
Date: Thu, 07 Oct 2004 01:25:42 -0500 [thread overview]
Message-ID: <1097130340.24725.22.camel@spider.hotmonkeyporn.com> (raw)
In-Reply-To: <5.1.0.14.1.20041006224402.02071d28@celine>
[-- Attachment #1: Type: text/plain, Size: 2825 bytes --]
On Thu, 2004-10-07 at 00:48, Ray Olszewski wrote:
> At 10:07 AM 10/7/2004 +0800, Peter wrote:
> >Want to free memory?
> >
> >$ free
> > total used free shared buffers cached
> >Mem: 223708 220120 3588 0 28356 107936
> >-/+ buffers/cache: 83828 139880
> >Swap: 128480 3996 124484
> >
> >$ locate /usr/bin/f* or x* or g* ...
> >
> >
> >$ free
> > total used free shared buffers cached
> >Mem: 223708 41364 182344 0 1520 28592
> >-/+ buffers/cache: 11252 212456
> >Swap: 128480 5056 123424
>
> Peter -- This is a pretty strange consequence of running the "locate"
> command. And I cannot replicate it here. For example:
>
> ray@waverly:~$ free
> total used free shared buffers cached
> Mem: 773892 742056 31836 0 87600 441912
> -/+ buffers/cache: 212544 561348
> Swap: 0 0 0
> ray@waverly:~$ locate /usr/bin/f*
> /usr/bin/factor
> [about 40 more lines, deleted here]
> ray@waverly:~$ free
> total used free shared buffers cached
> Mem: 773892 742076 31816 0 87608 441924
> -/+ buffers/cache: 212544 561348
> Swap: 0 0 0
>
> Any idea what's causing the change on your system? My understanding of
> Linux says it shouldn't work the way you report seeing it, so I'm wondering
> what I am missing.
It's not really anything to do with locate. You create an enormous
amount of memory pressure that won't be needed but the once. This
causes tho VM to dump most of what is in RAM to swap or just free the
pages.
I believe that is the LRU algorithm doing its job :)
In my case most of my applications were dumped to swap. X was still
snappy but almost everything else was massively sluggish and locate ate
all available memory plus a big chunk of swap.
spider ~ # free
total used free shared buffers cached
Mem: 1034704 1023732 10972 0 53008 334368
-/+ buffers/cache: 636356 398348
Swap: 2048248 25464 2022784
spider ~ # locate /usr/bin/g*
<snip>
spider ~ # free
total used free shared buffers cached
Mem: 1034704 132848 901856 0 652 36024
-/+ buffers/cache: 96172 938532
Swap: 2048248 252972 1795276
spider ~ #
--
Owen Ford <oford@arghblech.com>
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-07 6:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 5:01 Heavy load of graphics Ankit Jain
2004-10-05 5:45 ` Jeff Woods
2004-10-05 6:34 ` Ray Olszewski
2004-10-05 9:25 ` Geert Uytterhoeven
2004-10-05 10:04 ` Jim Nelson
2004-10-06 6:35 ` Ankit Jain
2004-10-06 21:02 ` Jim Nelson
2004-10-07 12:48 ` Ankit Jain
2004-10-07 22:00 ` Jim Nelson
2004-10-07 22:04 ` chuck gelm
2004-10-08 5:27 ` Ankit Jain
2004-10-08 14:37 ` Ray Olszewski
2004-10-05 12:26 ` chuck gelm
2004-10-05 16:25 ` Terrence Martin
2004-10-06 4:55 ` Ankit Jain
2004-10-07 1:50 ` chuck gelm
2004-10-07 2:07 ` Peter
2004-10-07 5:48 ` Ray Olszewski
2004-10-07 6:25 ` Owen Ford [this message]
2004-10-07 12:14 ` Ankit Jain
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=1097130340.24725.22.camel@spider.hotmonkeyporn.com \
--to=oford@arghblech.com \
--cc=linux-newbie@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