public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] vm swappiness with contest
Date: Tue, 31 Dec 2002 18:20:53 +1100	[thread overview]
Message-ID: <200212311820.53437.conman@kolivas.net> (raw)
In-Reply-To: <3E11426A.4ABE66B5@digeo.com>

On Tuesday 31 Dec 2002 6:08 pm, Andrew Morton wrote:
> Con Kolivas wrote:
> > ...
> > post usemem:
> > MemTotal:       257296 kB
> > MemFree:         86168 kB
> > Buffers:           392 kB
> > Cached:           2244 kB
> > SwapCached:        632 kB
> > Active:         159484 kB
> > Inactive:         1380 kB
> > HighTotal:           0 kB
> > HighFree:            0 kB
> > LowTotal:       257296 kB
> > LowFree:         86168 kB
> > SwapTotal:     4194272 kB
> > SwapFree:      4192668 kB
> > Dirty:              60 kB
> > Writeback:           0 kB
> > Mapped:           1768 kB
> > Slab:             6748 kB
> > Committed_AS:     6588 kB
> > PageTables:        196 kB
> > ReverseMaps:       619
>
> OK, thanks.   It's a memory leak.
>
> Could you please send me a detailed description of how to
> set about reproducing this?
>
> When you say "I ran contest for a few days till I recreated the problem
> and it did recur.", does this imply that the leak was really slowly
> increasing, or does it imply that everything was fine for a few days
> uptime and then it sudddenly leaked a large amount of memory?

I ran contest -n 100 -l all

which should run all loads 100 times. The dbench_load results remained pretty 
much static until about the 60th run and then it started increasing fairly 
rapidly.

dbench_load doesnt exist in contest 0.51, but running dbench_load by itself 
did NOT reproduce the problem - I tried this first. Dbench_load just seemed 
to notice it the most, so it's one of the other loads in contest exposing the 
leak which are all in v 0.51. Unfortunately I cant say for certain which of 
the loads it is.

Con

  reply	other threads:[~2002-12-31  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27  5:46 [BENCHMARK] vm swappiness with contest Con Kolivas
2002-12-27 10:00 ` Con Kolivas
2002-12-28  6:16   ` Con Kolivas
2002-12-28  6:26     ` Andrew Morton
2002-12-28  8:05     ` Linus Torvalds
2002-12-31  5:58     ` Con Kolivas
2002-12-31  6:08       ` Andrew Morton
2002-12-31  6:24         ` Con Kolivas
2002-12-31  6:37           ` Andrew Morton
2002-12-31  6:57             ` Con Kolivas
2002-12-31  7:08               ` Andrew Morton
2002-12-31  7:20                 ` Con Kolivas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-27 13:13 Paolo Ciarrocchi

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=200212311820.53437.conman@kolivas.net \
    --to=conman@kolivas.net \
    --cc=akpm@digeo.com \
    --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