public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	hugh@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: Benchmarking objrmap under memory pressure
Date: Tue, 13 Apr 2004 23:59:40 +0200	[thread overview]
Message-ID: <20040413215940.GD2150@dualathlon.random> (raw)
In-Reply-To: <20040413005111.71c7716d.akpm@osdl.org>

On Tue, Apr 13, 2004 at 12:51:11AM -0700, Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@aracnet.com> wrote:
> >
> > UP Athlon 2100+ with 512Mb of RAM. Rebooted clean before each test
> > then did "make clean; make vmlinux; make clean". Then I timed a
> > "make -j 256 vmlinux" to get some testing under mem pressure. 
> > 
> > I was trying to test the overhead of objrmap under memory pressure,
> > but it seems it's actually distinctly negative overhead - rather pleasing
> > really ;-) 
> > 
> > 2.6.5
> > 225.18user 30.05system 6:33.72elapsed 64%CPU (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs (37590major+2604444minor)pagefaults 0swaps
> > 
> > 2.6.5-anon_mm
> > 224.53user 26.00system 5:29.08elapsed 76%CPU (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs (29127major+2577211minor)pagefaults 0swaps
> 
> A four second reduction in system time caused a one minute reduction in
> runtime?  Pull the other one ;)
> 
> Average of five runs, please...

at the very least the 6 seconds difference on a ~6 minutes load between
anonvma and anonmm sounds smaller than the measurement error generated
by disk seeks for a swapping workload, so yes, I'd like to see all 5
runs (not just the average).

As for the difference between 2.6.5 and 2.6.5-anonvma, that might be the
memory saved by the removal of rmap that in turn reduces the swap-I/O
required to complete the load or something like that, so that one may
not be a measurement error but just the benefit of anon-vma or anonmm,
but for a 6 seconds difference during a swap load I'd definitely like to
see the 5 runs.

Thanks!

  parent reply	other threads:[~2004-04-13 21:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  7:39 Benchmarking objrmap under memory pressure Martin J. Bligh
2004-04-13  7:51 ` Andrew Morton
2004-04-13  7:55   ` Martin J. Bligh
2004-04-13 21:59   ` Andrea Arcangeli [this message]
2004-04-14  0:38   ` Martin J. Bligh
2004-04-14 16:27     ` Andrea Arcangeli
2004-04-14 16:42       ` Martin J. Bligh
2004-04-14 17:11         ` Andrea Arcangeli
2004-04-14 17:48       ` Hugh Dickins
2004-04-14 23:39         ` Andrea Arcangeli
2004-04-15 10:21           ` Hugh Dickins
2004-04-15 13:22             ` Andrea Arcangeli
2004-04-15 13:45               ` Hugh Dickins
2004-04-15 14:08                 ` Andrea Arcangeli
2004-04-15 16:23             ` Bill Davidsen
2004-04-15 16:48               ` Hugh Dickins
2004-04-22 19:54                 ` Bill Davidsen
2004-04-22 21:26                   ` Hugh Dickins
2004-04-14 18:11   ` Bill Davidsen

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=20040413215940.GD2150@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox