From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] duppage
Date: Sun, 8 Jun 2014 19:15:47 +0200 [thread overview]
Message-ID: <1808dc12a2ce7a6966c7f3128cfb8bb0@felloff.net> (raw)
In-Reply-To: <febeb72da75dd219fc0d15dbc8b6de89@ivey>
i get consistent results with iostats for building pc64.
(on amd64)
166 192 104916 0 0 /bin/rc
4 90 343308 0 0 /bin/awk
37 51 51280 0 0 /bin/echo
17 43 103786 0 0 /bin/sed
3 17 51567 0 0 /bin/ls
3 12 34624 0 0 /bin/grep
13 24 40114 0 0 /bin/cp
1 6 19112 0 0 /bin/pwd
4 15 40658 0 0 /bin/xd
128 192 263785 0 0 /bin/6c
5 34 113149 0 0 /bin/6l
4 27 89551 0 0 /bin/6a
1 10 33360 0 0 /bin/mkdir
2 9 22016 0 0 /bin/dd
4 18 55085 0 0 /bin/strip
1 17 62301 0 0 /bin/mkpaqfs
4 14 33797 0 0 /bin/rm
2 3 121 0 0 /bin/membername
2 15 46432 0 0 /bin/tr
1 19 72544 0 0 /bin/ar
1 4 10992 0 0 /bin/cat
2 24 86580 0 0 /bin/hoc
4 26 86433 0 0 /bin/file
4 13 33439 0 0 /bin/aux/data2s
1 7 23488 0 0 /bin/date
1 14 49502 0 0 /bin/size
1 25 94969 0 0 /bin/mk
i made a small test trying running echo 1,2,3 and 4 times
and i get exactly one additional read per exec (which
is the read of the file header) all the other pages
are cached.
with MCACHE mount, it is exactly the same amount of
reads no matter how often i run it. :)
but thats not loaded. is your machine starved of memory?
my guess would be that the cached pages getting uncached
and reused in your case. i remember fixing some bugs
in imagereclaim that could potentially cause this.
but thats all speculation...
theres a statistics struct there that you can peek on
from acid -k and see how often imagereclaim runs between
your test passes.
--
cinap
next prev parent reply other threads:[~2014-06-08 17:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 14:53 erik quanstrom
2014-06-08 17:15 ` cinap_lenrek [this message]
2014-06-08 17:22 ` Charles Forsyth
2014-06-08 17:34 ` erik quanstrom
2014-06-08 17:50 ` Charles Forsyth
2014-06-08 17:53 ` erik quanstrom
2014-06-08 17:54 ` cinap_lenrek
2014-06-08 18:15 ` erik quanstrom
2014-06-08 18:37 ` Charles Forsyth
2014-06-09 8:23 ` Charles Forsyth
2014-06-09 13:21 ` erik quanstrom
2014-06-10 1:35 ` erik quanstrom
2014-06-10 3:53 ` cinap_lenrek
2014-06-10 12:58 ` erik quanstrom
2014-06-10 13:56 ` Steve Simon
2014-06-10 15:30 ` erik quanstrom
2014-06-10 14:06 ` cinap_lenrek
2014-06-11 18:04 ` erik quanstrom
2014-06-08 17:49 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 23:55 erik quanstrom
2012-02-25 3:29 cinap_lenrek
2012-02-25 20:09 ` Charles Forsyth
2012-02-26 4:13 ` erik quanstrom
2012-02-29 10:31 ` Richard Miller
2012-02-29 14:14 ` cinap_lenrek
2012-02-29 19:35 ` Richard Miller
2012-02-29 19:50 ` cinap_lenrek
2012-03-03 9:58 ` Richard Miller
2012-03-03 19:30 ` cinap_lenrek
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=1808dc12a2ce7a6966c7f3128cfb8bb0@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).