From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <jens.axboe@oracle.com>, npiggin@suse.de, dgc@sgi.com
Subject: IO CPU Affinity: more results...
Date: Wed, 26 Mar 2008 14:24:09 -0400 [thread overview]
Message-ID: <47EA94C9.4060308@hp.com> (raw)
In-Reply-To: <20080326132806.GD15355@kernel.dk>
Current blk.git origin/io-cpu-affinity sources:
After 60 successful passes on a 4-way ia64:
60 0 mkfs untar make
60 1 mkfs untar make
Part RQ Min Avg Max Dev
----- -- ------- ------- ------- -------
mkfs 0 81.233 81.810 82.599 0.330
mkfs 1 81.083 81.854 82.973 0.405
untar 0 17.075 17.676 18.098 0.273
untar 1 16.975 17.570 18.128 0.288
make 0 24.231 24.380 24.541 0.085
make 1 24.116 24.312 24.459 0.073
----- -- ------- ------- ------- -------
comb 0 122.898 123.866 125.002 0.516
comb 1 122.620 123.736 125.156 0.521
===== == ======= ======= ======= =======
psys 0 2.12% 2.19% 2.28% 0.035
psys 1 1.92% 2.00% 2.25% 0.049
so:
1. It's working pretty solidly on ia64
2. We still see reduced combined times w/ rq=1 (albeit, not much - and certainly nothing definitive with the relatively high standard deviations).
3. We see large reduction in %system to do the same work - 8% less
And here's something else I've noticed: It seems that as the runs go on, the makes happen quicker (in general). I've got some graphs on free.linux.hp.com - they are a bit busy, but here are some pointers:
1. Black stuff is for rq=0, red stuff is for rq=1
2. Solid horizontal line indicates the set average.
3. Lower numbers for /all/ graphs are better
4. Open circles represent individual test run points
5. Hashed-line w/ shaded large circles represents localized averages: each circle is the average of the surrounding 5 data points.
The last thing is key: you'll see on
http://free.linux.hp.com/~adb/jens/make.png
The black hashed line (rq=0) tends to bop around the average, whilst the red hashed line (rq=1) seems to show a downwards trend. (I need to run this a lot longer to see if it holds up.) Note: this trending-downwards does /not/ appear in the mkfs & untar parts of the operations. /Every/ time I've had extended runs with rq=1 I see this trend.
Note: %sys doesn't really fluctuate much at all - as can be seen by:
http://free.linux.hp.com/~adb/jens/psys.png
The other graphs include:
http://free.linux.hp.com/~adb/jens/mkfs.png
http://free.linux.hp.com/~adb/jens/untar.png
http://free.linux.hp.com/~adb/jens/comb.png
Alan D. Brunelle
HP / OSLO / S&P
parent reply other threads:[~2008-03-26 18:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20080326132806.GD15355@kernel.dk>]
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=47EA94C9.4060308@hp.com \
--to=alan.brunelle@hp.com \
--cc=dgc@sgi.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.