From: William Lee Irwin III <wli@holomorphy.com>
To: "Bond, Andrew" <Andrew.Bond@hp.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: TPC-C benchmark used standard RH kernel
Date: Fri, 20 Sep 2002 13:56:53 -0700 [thread overview]
Message-ID: <20020920205653.GM3530@holomorphy.com> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E106402D09E43@cceexc18.americas.cpqcorp.net>
On Thu, Sep 19, 2002 at 02:27:22PM -0500, Bond, Andrew wrote:
> This isn't as recent as I would like, but it will give you an idea.
> Top 75 from readprofile. This run was not using bigpages though.
> Andy
> 00000000 total 7872 0.0066
> c0105400 default_idle 1367 21.3594
> c012ea20 find_vma_prev 462 2.2212
> c0142840 create_bounce 378 1.1250
> c0142540 bounce_end_io_read 332 0.9881
> c0197740 __make_request 256 0.1290
> c012af20 zap_page_range 231 0.1739
> c012e9a0 find_vma 214 1.6719
> c012e780 avl_rebalance 160 0.4762
Looks like you're doing a lot of mmapping or faulting requiring VMA
lookups, or the number of VMA's associated with a task makes the
various VMA manipulations extremely expensive.
Can you dump /proc/pid/maps on some of these processes?
Thanks,
Bill
next prev parent reply other threads:[~2002-09-20 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 19:27 TPC-C benchmark used standard RH kernel Bond, Andrew
2002-09-19 20:40 ` Dave Hansen
2002-09-20 17:20 ` Mike Anderson
2002-09-20 17:31 ` Jens Axboe
2002-09-20 18:05 ` Mike Anderson
2002-09-20 20:56 ` William Lee Irwin III [this message]
2002-09-20 22:07 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 17:43 Bond, Andrew
2002-09-19 21:18 Bond, Andrew
2002-09-19 21:48 ` Dave Hansen
2002-09-19 19:15 Bond, Andrew
2002-09-19 17:15 Bond, Andrew
2002-09-19 18:14 ` Dave Hansen
2002-09-19 19:05 ` Martin J. Bligh
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=20020920205653.GM3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Andrew.Bond@hp.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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