From: Mark <musicman529@yahoo.com>
To: xfs@oss.sgi.com
Subject: Fw: Re: XFS mkfs/mount options
Date: Wed, 18 Jun 2008 00:21:01 -0700 (PDT) [thread overview]
Message-ID: <521591.99815.qm@web34506.mail.mud.yahoo.com> (raw)
To all,
It appears I have found a defect in my testing. Generally, the procedure has been something like:
create filesystem
mount filesystem and set owner/group
run benchmark
alter some condition (CPU speed or IRQ routing)
re-run benchmark
compare results
The second run is contaminated by caching effects from the first run. This accounts for the roughly 5% speedup I saw after enabling explicit IRQ routing. Once I corrected this oversight, the difference became statistical noise.
My apologies to all for this red herring.
--
Mark
"What better place to find oneself than
on the streets of one's home village?"
--Capt. Jean-Luc Picard, "Family"
reply other threads:[~2008-06-18 7:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=521591.99815.qm@web34506.mail.mud.yahoo.com \
--to=musicman529@yahoo.com \
--cc=xfs@oss.sgi.com \
/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