From: Andrew Morton <akpm@linux-foundation.org>
To: "Styner, Douglas W" <douglas.w.styner@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tripathi, Sharad C" <sharad.c.tripathi@intel.com>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Ma, Chinang" <chinang.ma@intel.com>,
"Wang, Peter Xihong" <peter.xihong.wang@intel.com>,
"Nueckel, Hubert" <hubert.nueckel@intel.com>,
"Recalde, Luis F" <luis.f.recalde@intel.com>,
"Nelson, Doug" <doug.nelson@intel.com>,
"Cheng, Wu-sun" <wu-sun.cheng@intel.com>,
"Prickett, Terry O" <terry.o.prickett@intel.com>,
"Shunmuganathan,
Rajalakshmi" <rajalakshmi.shunmuganathan@intel.com>,
"Garg, Anil K" <anil.k.garg@intel.com>,
"Chilukuri, Harita" <harita.chilukuri@intel.com>,
"chris.mason@oracle.com" <chris.mason@oracle.com>
Subject: Re: Mainline kernel OLTP performance update
Date: Wed, 29 Apr 2009 00:29:30 -0700 [thread overview]
Message-ID: <20090429002930.b786348b.akpm@linux-foundation.org> (raw)
In-Reply-To: <D7C42C27E6CB1E4D8CBDF2F81EA92A2603459F3D6A@azsmsx501.amr.corp.intel.com>
On Tue, 28 Apr 2009 10:08:22 -0700 "Styner, Douglas W" <douglas.w.styner@intel.com> wrote:
> Summary: Measured the mainline kernel from kernel.org (2.6.30-rc3).
>
> The regression for 2.6.30-rc3 against the baseline, 2.6.24.2 is 1.91%. Oprofile reports 71.1626% user, 28.8295% system.
>
> Linux OLTP Performance summary
> Kernel# Speedup(x) Intr/s CtxSw/s us% sys% idle% iowait%
> 2.6.24.2 1.000 22106 43709 75 24 0 0
> 2.6.30-rc3 0.981 30645 43027 75 25 0 0
The main difference there is the interrupt frequency. Do we know which
interrupt source(s) caused this?
> Server configurations:
> Intel Xeon Quad-core 2.0GHz 2 cpus/8 cores/8 threads
> 64GB memory, 3 qle2462 FC HBA, 450 spindles (30 logical units)
>
>
> ======oprofile CPU_CLK_UNHALTED for top 30 functions
> Cycles% 2.6.24.2 Cycles% 2.6.30-rc3
> 74.8578 <database> 69.1925 <database>
ouch, that's a large drop in userspace CPU occupancy. It seems
inconsistent with the 1.91% above.
> 1.0500 qla24xx_start_scsi 1.1314 qla24xx_intr_handler
> 0.8089 schedule 1.0031 qla24xx_start_scsi
> 0.5864 kmem_cache_alloc 0.8476 __schedule
> 0.4989 __blockdev_direct_IO 0.6532 kmem_cache_alloc
> 0.4357 __sigsetjmp 0.4490 __blockdev_direct_IO
> 0.4152 copy_user_generic_string 0.4199 __sigsetjmp
> 0.3953 qla24xx_intr_handler 0.3946 __switch_to
> 0.3850 memcpy 0.3538 __list_add
> 0.3596 scsi_request_fn 0.3499 task_rq_lock
> 0.3188 __switch_to 0.3402 scsi_request_fn
> 0.2889 lock_timer_base 0.3382 rb_get_reader_page
> 0.2750 memmove 0.3363 copy_user_generic_string
> 0.2519 task_rq_lock 0.3324 aio_complete
> 0.2474 aio_complete 0.3110 try_to_wake_up
> 0.2460 scsi_alloc_sgtable 0.2877 ring_buffer_consume
> 0.2445 generic_make_request 0.2683 mod_timer
> 0.2263 qla2x00_process_completed_re0.2605 qla2x00_process_completed_re
> 0.2118 blk_queue_end_tag 0.2566 blk_queue_end_tag
> 0.2085 dio_bio_complete 0.2566 generic_make_request
> 0.2021 e1000_xmit_frame 0.2547 tcp_sendmsg
> 0.2006 __end_that_request_first 0.2372 lock_timer_base
> 0.1954 generic_file_aio_read 0.2333 memmove
> 0.1949 kfree 0.2294 memset_c
> 0.1915 tcp_sendmsg 0.2080 mempool_free
> 0.1901 try_to_wake_up 0.2022 generic_file_aio_read
> 0.1895 kref_get 0.1963 scsi_device_unbusy
> 0.1864 __mod_timer 0.1963 plist_del
> 0.1863 thread_return 0.1944 dequeue_rt_stack
> 0.1854 math_state_restore 0.1924 e1000_xmit_frame
next prev parent reply other threads:[~2009-04-29 7:40 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:08 Mainline kernel OLTP performance update Styner, Douglas W
2009-04-29 7:29 ` Andrew Morton [this message]
2009-04-29 8:28 ` Andi Kleen
2009-04-29 16:00 ` Styner, Douglas W
2009-04-29 16:06 ` Wilcox, Matthew R
2009-04-29 16:19 ` Andi Kleen
2009-04-29 15:48 ` Styner, Douglas W
2009-04-29 16:07 ` Andrew Morton
2009-04-29 16:25 ` Peter Zijlstra
2009-04-29 17:46 ` Chris Mason
2009-04-29 18:06 ` Pallipadi, Venkatesh
2009-04-29 18:25 ` Styner, Douglas W
2009-04-29 17:52 ` Styner, Douglas W
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 18:26 Ma, Chinang
2009-05-04 15:54 Styner, Douglas W
2009-05-06 6:29 ` Anirban Chakraborty
2009-05-06 15:53 ` Wilcox, Matthew R
2009-05-06 18:05 ` Styner, Douglas W
2009-05-06 18:12 ` Wilcox, Matthew R
2009-05-06 18:24 ` Anirban Chakraborty
2009-05-06 19:25 ` Wilcox, Matthew R
2009-05-06 18:19 ` Styner, Douglas W
2009-04-28 17:22 Styner, Douglas W
2009-04-23 16:49 Styner, Douglas W
2009-04-27 7:02 ` Andi Kleen
2009-04-28 16:57 ` Chuck Ebbert
2009-04-28 17:15 ` James Bottomley
2009-04-28 17:17 ` Styner, Douglas W
2009-01-13 21:10 Ma, Chinang
2009-01-13 22:44 ` Wilcox, Matthew R
2009-01-15 0:35 ` Andrew Morton
2009-01-15 1:21 ` Matthew Wilcox
2009-01-15 2:04 ` Andrew Morton
2009-01-15 2:27 ` Steven Rostedt
2009-01-15 7:11 ` Ma, Chinang
2009-01-19 18:04 ` Chris Mason
2009-01-19 18:37 ` Steven Rostedt
2009-01-19 18:55 ` Chris Mason
2009-01-19 19:07 ` Steven Rostedt
2009-01-19 23:40 ` Ingo Molnar
2009-01-15 2:39 ` Andi Kleen
2009-01-15 2:47 ` Matthew Wilcox
2009-01-15 3:36 ` Andi Kleen
2009-01-20 13:27 ` Jens Axboe
[not found] ` <588992150B702C48B3312184F1B810AD03A497632C@azsmsx501.amr.corp.intel.com>
2009-01-22 11:29 ` Jens Axboe
[not found] ` <588992150B702C48B3312184F1B810AD03A4F59632@azsmsx501.amr.corp.intel.com>
2009-01-27 8:28 ` Jens Axboe
2009-01-15 7:24 ` Nick Piggin
2009-01-15 9:46 ` Pekka Enberg
2009-01-15 13:52 ` Matthew Wilcox
2009-01-15 14:42 ` Pekka Enberg
2009-01-16 10:16 ` Pekka Enberg
2009-01-16 10:21 ` Nick Piggin
2009-01-16 10:31 ` Pekka Enberg
2009-01-16 10:42 ` Nick Piggin
2009-01-16 10:55 ` Pekka Enberg
2009-01-19 7:13 ` Nick Piggin
2009-01-19 8:05 ` Pekka Enberg
2009-01-19 8:33 ` Nick Piggin
2009-01-19 8:42 ` Nick Piggin
2009-01-19 8:47 ` Pekka Enberg
2009-01-19 8:57 ` Nick Piggin
2009-01-19 9:48 ` Pekka Enberg
2009-01-19 10:03 ` Nick Piggin
2009-01-16 20:59 ` Christoph Lameter
2009-01-16 0:27 ` Andrew Morton
2009-01-16 4:03 ` Nick Piggin
2009-01-16 4:12 ` Andrew Morton
2009-01-16 6:46 ` Nick Piggin
2009-01-16 6:55 ` Matthew Wilcox
2009-01-16 7:06 ` Nick Piggin
2009-01-16 7:53 ` Zhang, Yanmin
2009-01-16 10:20 ` Andi Kleen
2009-01-20 5:16 ` Zhang, Yanmin
2009-01-21 23:58 ` Christoph Lameter
2009-01-22 8:36 ` Zhang, Yanmin
2009-01-22 9:15 ` Pekka Enberg
2009-01-22 9:28 ` Zhang, Yanmin
2009-01-22 9:47 ` Pekka Enberg
2009-01-23 3:02 ` Zhang, Yanmin
2009-01-23 6:52 ` Pekka Enberg
2009-01-23 8:06 ` Pekka Enberg
2009-01-23 8:30 ` Zhang, Yanmin
2009-01-23 8:40 ` Pekka Enberg
2009-01-23 9:46 ` Pekka Enberg
2009-01-23 15:22 ` Christoph Lameter
2009-01-23 15:31 ` Pekka Enberg
2009-01-23 15:55 ` Christoph Lameter
2009-01-23 16:01 ` Pekka Enberg
2009-01-24 2:55 ` Zhang, Yanmin
2009-01-24 7:36 ` Pekka Enberg
2009-02-12 5:22 ` Zhang, Yanmin
2009-02-12 5:47 ` Zhang, Yanmin
2009-02-12 15:25 ` Christoph Lameter
2009-02-12 16:07 ` Pekka Enberg
2009-02-12 16:03 ` Pekka Enberg
2009-01-26 17:36 ` Christoph Lameter
2009-02-01 2:52 ` Zhang, Yanmin
2009-01-23 8:33 ` Nick Piggin
2009-01-23 9:02 ` Zhang, Yanmin
2009-01-16 7:00 ` Andrew Morton
2009-01-16 7:25 ` Nick Piggin
2009-01-16 8:59 ` Nick Piggin
2009-01-16 18:11 ` Rick Jones
2009-01-19 7:43 ` Nick Piggin
2009-01-19 22:19 ` Rick Jones
2009-01-15 14:12 ` James Bottomley
2009-01-15 17:44 ` Andrew Morton
2009-01-15 18:00 ` Matthew Wilcox
2009-01-15 18:14 ` Steven Rostedt
2009-01-15 18:44 ` Gregory Haskins
2009-01-15 18:46 ` Wilcox, Matthew R
2009-01-15 19:44 ` Ma, Chinang
2009-01-16 18:14 ` Gregory Haskins
2009-01-16 19:09 ` Steven Rostedt
2009-01-20 12:45 ` Gregory Haskins
2009-01-15 19:28 ` Ma, Chinang
2009-01-15 16:48 ` Ma, Chinang
2009-01-12 18:30 Ma, Chinang
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=20090429002930.b786348b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=anil.k.garg@intel.com \
--cc=arjan@linux.intel.com \
--cc=chinang.ma@intel.com \
--cc=chris.mason@oracle.com \
--cc=doug.nelson@intel.com \
--cc=douglas.w.styner@intel.com \
--cc=harita.chilukuri@intel.com \
--cc=hubert.nueckel@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.f.recalde@intel.com \
--cc=matthew.r.wilcox@intel.com \
--cc=peter.xihong.wang@intel.com \
--cc=rajalakshmi.shunmuganathan@intel.com \
--cc=sharad.c.tripathi@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=terry.o.prickett@intel.com \
--cc=wu-sun.cheng@intel.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;
as well as URLs for NNTP newsgroup(s).