From: Samium Gromoff <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: marcelo@brutus.conectiva.com.br, riel@surriel.com
Subject: pmap revisited
Date: Tue, 4 Sep 2001 03:13:34 +0000 (UTC) [thread overview]
Message-ID: <200109040313.f843DYc00623@vegae.deep.net> (raw)
Ashes on my head guys...
Gotta wrong results in my previous perftest... (slightly different
environments), so these are to be sure that on low VM load there isnt
any significant difference...
Here are new and revisited. Actually i maked sure that the environments
differs only in kernels...
Bonus: two bugs! :)
1. Quintela`s (shmtest of memtest) and pmap{2,3} == 100% instant deadlock
plain ac12 demonstrates ignorance.
2. Swapoff oops 100% - only in pmap3! (okay, swapoff of reiserfs
to be strict, but i think that doesnt actually matters)
swapoff oops will be in next mail.
Revisited results:
time find / -xdev - done 5 times
pmap 3
real 1m5.175s
real 1m4.699s
real 1m3.579s
============================
pmap 2
real 1m5.039s
real 1m4.779s
real 1m4.506s
============================
plain
real 1m4.820s
real 1m4.433s
real 1m4.285s
* fillmem == (fillmem of memtest)
* dont count on differences - they are quite flaky, one is only known:
there are no much difference anyways...
time fillmem - done 7 times, still giving strange results sometimes...
pmap 3
real 1m2.709s
real 1m2.417s
real 1m1.371s
real 1m1.241s
real 1m0.235s
(1m3.~, 1m4.5~) - add results
============================
pmap 2
real 1m5.294s
real 1m5.169s
real 1m4.431s
real 1m3.878s
real 1m3.523s
(1m6.~, 1m0.~, 1m3.355) - add results
============================
plain
real 1m1.570s
real 1m1.063s
real 1m1.007s
real 1m0.201s
real 0m59.677s
next reply other threads:[~2001-09-03 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 3:13 Samium Gromoff [this message]
2001-09-04 16:16 ` pmap revisited Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 4:07 Samium Gromoff
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=200109040313.f843DYc00623@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@brutus.conectiva.com.br \
--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