mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samium Gromoff <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: riel@surriel.com
Subject: Rik`s ac12-pmap2 vs ac12-vanilla perfcomp
Date: Sun, 2 Sep 2001 17:10:35 +0000 (UTC)	[thread overview]
Message-ID: <200109021710.f82HAbD00606@vegae.deep.net> (raw)

         Hello there, i just came with some benchmarks:
   Done on p166-24M
 
   No flames please - i know these were low VM loads, i did this just to know 
how big is test rmaps maitenance overhead. It shows us that even on low VM
load there is a huge win in using rmap. And the win increases with the VM load.
   Algo:
      - booted ac12
      - performed test A 7 times, then test B 7 times.
      - booted ac12-pmap2
      - performed test A 7 times, then test B 7 times.

      * each test was done 7 times, with the lowest and highest thrown away.
      * due to high values of data and streaming usage pattern caching was 
 unable to affect results, so it was ignored.

test A:
"time find / -xdev" + (standard junk eating ~6% cpu (top procinfo))
  descr: extremely low VM load, mostly IO dependent

test B:
"time find / -xdev | grep --regexp="\/" | xargs echo" + background mpg123 +
 + standard junk described above
  descr: low, although higher than A, vm load (nearly absolutely no swap)

Results:
        ac12            ac12-pmap2
===[ test A: find / -xdev
real    1m4.221s        0m56.916s
real    1m3.042s        0m57.275s
real    1m3.613s        0m57.606s
real    1m3.442s        0m57.166s
real    1m3.447s        0m56.895s
======================================
avg     63.553 sec      57.171 sec	11% win

sys     0m36.750s       0m31.980s
sys     0m37.190s       0m31.870s
sys     0m36.720s       0m32.300s
sys     0m36.650s       0m32.400s
sys     0m37.350s       0m32.270s
======================================
avg     36.93 sec       32.16 sec	13% win



===[ test B: find / -xdev | grep --regexp="\/" | xargs echo (with mpg123 in bgrnd
 eating 4M+ buf + 15-20% CPU)
real    0m38.720s       0m31.018s
real    0m38.061s       0m30.318s
real    0m38.075s       0m31.980s
real    0m37.626s       0m31.149s
real    0m38.431s       0m30.820s
======================================
avg     38.182 sec      31.057 sec	19% win

sys     0m16.090s       0m13.910s
sys     0m15.820s       0m13.610s
sys     0m15.750s       0m13.710s
sys     0m15.700s       0m13.780s
sys     0m15.750s       0m13.790s
======================================
avg     15.82 sec       13.76 sec	14% win



cheers,
 Sam

             reply	other threads:[~2001-09-02 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02 17:10 Samium Gromoff [this message]
2001-09-02 13:11 ` Rik van Riel
2001-09-02 17:04 ` Daniel Phillips
2001-09-02 21:46   ` Samium Gromoff
2001-09-02 17:51     ` Daniel Phillips
2001-09-02 22:18       ` Samium Gromoff
2001-09-03 15:22       ` Marcelo Tosatti
2001-09-03  9:58   ` Rik van Riel

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=200109021710.f82HAbD00606@vegae.deep.net \
    --to=_deepfire@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.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

all inboxes | Powered by JetHome®