From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] duppage
Date: Sun, 8 Jun 2014 10:53:36 -0400 [thread overview]
Message-ID: <febeb72da75dd219fc0d15dbc8b6de89@ivey> (raw)
i was experimenting a bit with cinap's version of dropping duppage, and for
the lame build the kernel tests there's quite a bit more i/o
duppage no duppage
read 45976291 53366962
rpc 73674 75718
you can see below that both end up reading 6909416 bytes
from 6c for 136 executions. 6c is only 264450 text+data,
so that's 26 unnecessary reads (6c had already been cached).
the original fairs better reading only 1816296, but that's
still way too much.
this needs a better algorithm.
- erik
---
without duppage
Opens Reads (bytes) Writes (bytes) File
4 43 301801 0 0 /bin/ape/sh
3 12 61137 0 0 /bin/ls
155 476 1642711 0 0 /bin/rc
5 84 602660 0 0 /bin/awk
9 79 514294 0 0 /bin/6a
136 1060 6909416 0 0 /bin/6c
5 50 329397 0 0 /bin/6l
8 20 66901 0 0 /bin/echo
3 11 51238 0 0 /bin/xd
3 13 72700 0 0 /bin/sed
4 13 54357 0 0 /bin/cp
4 33 201057 0 0 /bin/file
4 21 125962 0 0 /bin/strip
4 12 51024 0 0 /bin/aux/data2s
2 9 42686 0 0 /bin/rm
with duppage
Opens Reads (bytes) Writes (bytes) File
4 31 216169 0 0 /bin/ape/sh
3 10 50833 0 0 /bin/ls
155 190 210423 0 0 /bin/rc
5 57 398636 0 0 /bin/awk
9 57 357441 0 0 /bin/6a
136 370 1816296 0 0 /bin/6c
5 29 178269 0 0 /bin/6l
8 13 35485 0 0 /bin/echo
3 11 59756 0 0 /bin/sed
3 9 40742 0 0 /bin/xd
4 10 39909 0 0 /bin/cp
4 18 100617 0 0 /bin/file
4 12 60634 0 0 /bin/strip
4 9 37104 0 0 /bin/aux/data2s
2 8 38150 0 0 /bin/rm
next reply other threads:[~2014-06-08 14:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 14:53 erik quanstrom [this message]
2014-06-08 17:15 ` cinap_lenrek
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=febeb72da75dd219fc0d15dbc8b6de89@ivey \
--to=quanstro@quanstro.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).