From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: accuracy of btt result on btreplay?
Date: Wed, 03 Mar 2010 14:05:33 +0000 [thread overview]
Message-ID: <1267625133.2926.13.camel@cail> (raw)
In-Reply-To: <398d69301003022341r5840a9e1g492c243c330bd398@mail.gmail.com>
Hi Xuekun -
Not sure why they Q2Q N value is down 5%, but the AVG Q2Q is pretty
close - only 11msec (again, about 5%). After that, things are affected
by merge rates most likely - note that there were 262882 merges on the
first run whilst there were only 8970 on the second run. Perhaps you
could look at the blkparse output from both and get a feel for the vast
reduction in merges. [Any changes on the system between the runs?]
Regards,
Alan
next prev parent reply other threads:[~2010-03-03 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
2010-03-03 14:05 ` Alan D. Brunelle [this message]
2010-03-04 1:37 ` Xuekun Hu
2010-03-05 7:30 ` Xuekun Hu
2010-03-08 8:38 ` Xuekun Hu
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=1267625133.2926.13.camel@cail \
--to=alan.brunelle@hp.com \
--cc=linux-btrace@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