All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: alan@cotse.com
Cc: linux-kernel@vger.kernel.org, vs@namesys.com
Subject: Re: [BENCHMARK] 2.5.46-mm1 with contest
Date: Mon, 11 Nov 2002 13:03:46 -0800	[thread overview]
Message-ID: <3DD01B32.4A113A71@digeo.com> (raw)
In-Reply-To: YWxhbg==.a11f3fbc6d68c50c7f190513c1d3bacf@1037045821.cotse.net

Alan Willis wrote:
> 
>    Attached are the slabinfo, meminfo, and output of vmstat 1.  My system
> was almost unusable at the time, so I got what I could.  I don't have
> anything in my crontab.  This morning my system had been sitting
> quietly all weekend, I did a few things, and then removed a large
> directory and untarred 2.5.47, less than a minute after which my system
> got unbearably slow.
> 
>   It should be noted that I have a 2.5.46 + reiser4 patches, which I think
> made a few changes under mm/.  I also had a reiser4 partition mounted at
> the time, with slightly under 1 million empty files in it.  I hadn't
> accessed it in a while though.
> 


MemTotal:       251332 kB
MemFree:          1748 kB
MemShared:           0 kB
Buffers:           352 kB
Cached:          30040 kB

This is presumably active mmapped memory.  executable text.

SwapCached:      41748 kB
Active:         165064 kB

That's a lot of active memory.

Inactive:          976 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       251332 kB
LowFree:          1748 kB
SwapTotal:     1028152 kB
SwapFree:       834084 kB
Dirty:               0 kB
Writeback:           0 kB
Mapped:         164592 kB

That's an awful lot of mapped memory.  Have you been altering
/proc/sys/vm/swappiness?  Has some application run berzerk
and used tons of memory?

Slab:             7592 kB
Committed_AS:   423120 kB
PageTables:       1996 kB
ReverseMaps:     69425
HugePages_Total:    15
HugePages_Free:     15
Hugepagesize:     4096 kB

You've lost 60 megabytes in hugepages!  Bill's patch (which is in .47)
changes the initial number of hugetlb pages to zero, which is rather
kinder.

So I don't _think_ there's a leak here.  It could be that your
normal workload fits OK ito 256 megs, but thrashes when it is
squeezed into 196 megs.

Suggest you do `echo 0 > /proc/sys/vm/nr_hugepages' and retest.

  parent reply	other threads:[~2002-11-11 20:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08  0:32 [BENCHMARK] 2.5.46-mm1 with contest Alan Willis
2002-11-08  0:48 ` Andrew Morton
2002-11-08 21:08   ` Alan Willis
2002-11-08 21:21     ` Andrew Morton
     [not found]       ` <YWxhbg==.a11f3fbc6d68c50c7f190513c1d3bacf@1037045821.cotse.net>
2002-11-11 21:03         ` Andrew Morton [this message]
2002-11-11 21:11           ` Alan Willis
2002-11-11 21:32             ` Andrew Morton
2002-11-13  0:14               ` Denis Vlasenko
2002-11-12 20:07                 ` Alan Willis
  -- strict thread matches above, loose matches on Subject: below --
2002-11-07 22:53 Con Kolivas
2002-11-07 23:48 ` Robert Love
2002-11-07 23:58   ` Andrew Morton
2002-11-08  0:04     ` Robert Love
2002-11-08  6:04       ` Con Kolivas
2002-11-08  0:10     ` Benjamin LaHaise

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=3DD01B32.4A113A71@digeo.com \
    --to=akpm@digeo.com \
    --cc=alan@cotse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vs@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.