From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] interesting timing tests
Date: Sat, 19 Jun 2010 21:36:23 -0400 [thread overview]
Message-ID: <339274c87be111df807b4bde17033814@kw.quanstro.net> (raw)
In-Reply-To: <3f9d3a9e596e4e5a0d72faa153814e31@hamnavoe.com>
On Sat Jun 19 09:44:25 EDT 2010, 9fans@hamnavoe.com wrote:
> > note the extreme system time on the 16 processor machine
>
> kprof(3)
i'm not sure i completely trust kprof these days. there
seems to be a lot of sampling error. the last time i tried to
use it to get timing on esp, encryption didn't show up at all
in kprof's output. trace(3) showed that encryption was 80%
of the total cpu use. in any event, i was suspecting that ilock
would be a big loser as nproc goes up, and it does appear to
be. i'm less sure that runproc is really using 62% of the cpu
c; kprof /386/9pccpu /dev/kpdata
total: 70023 in kernel text: 65773 outside kernel text: 4250
KTZERO f0100000
ms % sym
40984 62.3 runproc
9930 15.0 ilock
5720 8.6 _cycles
4360 6.6 perfticks
1784 2.7 isaconfig
1600 2.4 iunlock
cf. the 4 processor 5600 xeon:
b; kprof /386/9pccpu /dev/kpdata
total: 14416 in kernel text: 11434 outside kernel text: 2982
KTZERO f0100000
ms % sym
4036 35.2 rebalance
2483 21.7 runproc
1561 13.6 _cycles
918 8.0 perfticks
377 3.2 unlock
337 2.9 microdelay
259 2.2 idlehands
- erik
next prev parent reply other threads:[~2010-06-20 1:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 23:26 erik quanstrom
2010-06-19 13:42 ` Richard Miller
2010-06-20 1:36 ` erik quanstrom [this message]
2010-06-20 7:44 ` Richard Miller
2010-06-20 12:45 ` erik quanstrom
2010-06-20 16:51 ` Richard Miller
2010-06-20 21:55 ` erik quanstrom
2010-06-21 1:41 ` erik quanstrom
2010-06-21 3:46 ` Venkatesh Srinivas
2010-06-21 14:40 ` erik quanstrom
2010-06-21 16:42 ` Venkatesh Srinivas
2010-06-21 16:43 ` erik quanstrom
2010-06-21 21:11 ` Bakul Shah
2010-06-21 21:21 ` erik quanstrom
2010-06-21 21:47 ` Bakul Shah
2010-06-21 22:16 ` erik quanstrom
2010-06-22 3:24 ` Lawrence E. Bakst
2010-06-23 1:09 ` erik quanstrom
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=339274c87be111df807b4bde17033814@kw.quanstro.net \
--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).