From: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
linux-kernel@vger.kernel.org, garloff@suse.de, ak@suse.de,
Ian.Pratt@cl.cam.ac.uk
Subject: Re: 2.6.11 vs 2.6.10 slowdown on i686
Date: Thu, 17 Mar 2005 20:23:23 +0000 [thread overview]
Message-ID: <E1DC1Wd-00011q-00@mta1.cl.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 17 Mar 2005 23:37:24 +1100." <42397A04.2060703@yahoo.com.au>
> There are some changes in the current -bk tree (which are a
> bit in-flux at the moment) which introduce some optimisations.
>
> They should bring 2-level performance close to par with 2.6.10.
> If not, complain again :)
The good news is that with a BK snapshot from today
[md5key=4238cb8e36_Z5Cgys8rTovspboIJpw] performance is rather
improved relative to 2.6.11 :
fork: 166 -> 187 -13%
exec: 857 -> 909 -6%
Rather better than -40%, but still not brilliant.
Any more improvements in the pipeline?
Ian
------------------------------------------------------------------------------
Host OS Mhz null null open slct sig sig fork exec sh
call I/O stat clos TCP inst hndl proc proc proc
--------- ------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
commando- Linux 2.6.10 2400 0.49 0.57 2.06 3.06 19.6 0.89 2.70 166. 857. 2972
commando- Linux 2.6.12 2400 0.49 0.60 2.37 3.43 20.9 0.91 2.64 187. 909. 3076
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ------ ------ ------ ------ ------ ------- -------
commando- Linux 2.6.10 7.5800 4.3300 8.1900 5.1100 33.1 8.37000 41.9
commando- Linux 2.6.12 7.7400 7.9200 8.3700 5.1600 27.0 9.32000 36.5
*Local* Communication latencies in microseconds - smaller is better
---------------------------------------------------------------------
Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP
ctxsw UNIX UDP TCP conn
--------- ------------- ----- ----- ---- ----- ----- ----- ----- ----
commando- Linux 2.6.10 7.750 19.4 21.3 37.2 45.5 42.5 53.2 76.
commando- Linux 2.6.12 7.740 18.2 23.1 37.4 45.6 42.6 54.9 80.
File & VM system latencies in microseconds - smaller is better
-------------------------------------------------------------------------------
Host OS 0K File 10K File Mmap Prot Page 100fd
Create Delete Create Delete Latency Fault Fault selct
--------- ------------- ------ ------ ------ ------ ------- ----- ------- -----
commando- Linux 2.6.10 39.3 16.2 92.7 35.2 122.0 1.200 2.14310 18.3
commando- Linux 2.6.12 38.7 16.4 94.1 35.1 148.0 1.029 2.25100 18.0
*Local* Communication bandwidths in MB/s - bigger is better
-----------------------------------------------------------------------------
Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem
UNIX reread reread (libc) (hand) read write
--------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- -----
commando- Linux 2.6.10 313. 440. 222. 1551.7 1528.5 549.1 566.8 1550 784.8
commando- Linux 2.6.12 556. 477. 224. 1540.3 1551.4 566.5 566.6 1551 786.2
next prev parent reply other threads:[~2005-03-17 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 12:16 Ian Pratt
2005-03-17 12:37 ` Nick Piggin
2005-03-17 20:23 ` Ian Pratt [this message]
2005-03-18 8:25 ` Kurt Garloff
2005-03-18 8:46 ` Nick Piggin
2005-03-17 18:36 ` Andi Kleen
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=E1DC1Wd-00011q-00@mta1.cl.cam.ac.uk \
--to=ian.pratt@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®