public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Ingo Molnar'" <mingo@elte.hu>,
	"'Linus Torvalds'" <torvalds@osdl.org>,
	"'Andrew Morton'" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Industry db benchmark result on recent 2.6 kernels
Date: Sat, 02 Apr 2005 12:12:24 +1000	[thread overview]
Message-ID: <424DFF88.30003@yahoo.com.au> (raw)
In-Reply-To: <200504020100.j3210fg04870@unix-os.sc.intel.com>

Chen, Kenneth W wrote:
> Ingo Molnar wrote on Thursday, March 31, 2005 8:52 PM
> 
>>the current defaults for cache_hot_time are 10 msec for NUMA domains,
>>and 2.5 msec for SMP domains. Clearly too low for CPUs with 9MB cache.
>>Are you increasing cache_hot_time in your experiment? If that solves
>>most of the problem that would be an easy thing to fix for 2.6.12.
> 
> 
> 
> Chen, Kenneth W wrote on Thursday, March 31, 2005 9:15 PM
> 
>>Yes, we are increasing the number in our experiments.  It's in the queue
>>and I should have a result soon.
> 
> 
> Hot of the press: bumping up cache_hot_time to 10ms on our db setup brings
> 2.6.11 performance on par with 2.6.9.  Theory confirmed.
> 

OK, that's good. I'll look at whether we can easily use Ingo's
tool on the SMP domain only, to avoid the large O(n^2). That might
be an acceptable short term solution for 2.6.12.

If you get a chance to also look at those block layer patches that
would be good - if they give you a nice improvement, that would
justify getting them into -mm.

-- 
SUSE Labs, Novell Inc.


  reply	other threads:[~2005-04-02  2:12 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02  1:00 Industry db benchmark result on recent 2.6 kernels Chen, Kenneth W
2005-04-02  2:12 ` Nick Piggin [this message]
2005-04-02 14:53 ` [patch] sched: auto-tune migration costs [was: Re: Industry db benchmark result on recent 2.6 kernels] Ingo Molnar
2005-04-02 21:22   ` Paul Jackson
2005-04-03  5:53   ` Paul Jackson
2005-04-03  7:04     ` Ingo Molnar
2005-04-03  8:15       ` Paul Jackson
2005-04-03 11:34       ` Paul Jackson
2005-04-03 14:12         ` Paul Jackson
2005-04-03 15:01           ` Ingo Molnar
2005-04-03 22:30             ` Paul Jackson
2005-04-05  6:53               ` [patch] sched: auto-tune migration costs Andi Kleen
2005-04-05  7:20                 ` Paul Jackson
2005-04-03 15:24           ` [patch] sched: auto-tune migration costs [was: Re: Industry db benchmark result on recent 2.6 kernels] Ingo Molnar
2005-04-03 23:08             ` Paul Jackson
2005-04-04  2:08               ` Nick Piggin
2005-04-04  3:55                 ` Paul Jackson
2005-04-04  5:45                   ` Ingo Molnar
2005-04-04  5:50                     ` Paul Jackson
2005-04-04  5:56                   ` Nick Piggin
2005-04-04  6:38                     ` Paul Jackson
2005-04-04  6:48                       ` Ingo Molnar
2005-04-04  7:37                         ` Paul Jackson
2005-04-04  6:50               ` Ingo Molnar
2005-04-04  7:27                 ` Paul Jackson
2005-04-03 14:29         ` Ingo Molnar
2005-04-03 23:15           ` Paul Jackson
2005-04-04  1:31           ` Chen, Kenneth W
2005-04-04  6:24             ` Ingo Molnar
2005-04-04  6:39               ` Ingo Molnar
2005-04-06  0:08               ` Chen, Kenneth W
2005-04-04  4:25         ` Andy Lutomirski
2005-04-04  4:36           ` Paul Jackson
2005-04-04  1:11       ` Chen, Kenneth W
2005-04-04 11:37         ` Ingo Molnar
2005-04-04 17:27           ` Paul Jackson
2005-04-05  1:43           ` Chen, Kenneth W
2005-04-05  1:49             ` Ingo Molnar
2005-04-05  3:04               ` Ingo Molnar
2005-04-06  3:33                 ` Chen, Kenneth W
2005-04-06  6:45                   ` Ingo Molnar
2005-04-08  2:27                     ` Chen, Kenneth W
2005-04-03  9:01     ` Paul Jackson
  -- strict thread matches above, loose matches on Subject: below --
2005-04-01 16:34 Industry db benchmark result on recent 2.6 kernels Manfred Spraul
2005-03-28 19:33 Chen, Kenneth W
2005-03-28 19:50 ` Dave Hansen
2005-03-28 20:01   ` Chen, Kenneth W
2005-03-30  0:00 ` Linus Torvalds
2005-03-30  0:22   ` Chen, Kenneth W
2005-03-30  0:46   ` Chen, Kenneth W
2005-03-30  0:57     ` Linus Torvalds
2005-03-30  1:31       ` Nick Piggin
2005-03-30  1:38         ` Chen, Kenneth W
2005-03-30  1:56           ` Nick Piggin
2005-03-31 14:14           ` Ingo Molnar
2005-03-31 19:53             ` Chen, Kenneth W
2005-03-31 20:05               ` Linus Torvalds
2005-03-31 20:08                 ` Linus Torvalds
2005-03-31 22:14                   ` Chen, Kenneth W
2005-03-31 23:35                     ` Nick Piggin
2005-04-01  6:05                       ` Paul Jackson
2005-04-01  6:34                         ` Nick Piggin
2005-04-01  7:19                           ` Paul Jackson
2005-04-01  6:46                         ` Ingo Molnar
2005-04-01 22:32                           ` Chen, Kenneth W
2005-04-01 22:51                             ` Linus Torvalds
2005-04-02  2:19                               ` Nick Piggin
2005-04-04  1:40                               ` Kevin Puetz
2005-04-02  1:44                             ` Paul Jackson
2005-04-02  2:05                               ` Chen, Kenneth W
2005-04-02  2:38                                 ` Paul Jackson
2005-04-03  6:36                                 ` David Lang
2005-04-03  6:53                                   ` Andreas Dilger
2005-04-03  7:23                                     ` David Lang
2005-04-03  7:38                                       ` Nick Piggin
2005-04-01  6:59                         ` Ingo Molnar
2005-04-01  9:29                           ` Paul Jackson
2005-04-01 10:34                             ` Ingo Molnar
2005-04-01 14:39                               ` Paul Jackson
2005-04-01  4:52                     ` Ingo Molnar
2005-04-01  5:14                       ` Chen, Kenneth W
2005-04-01 22:51   ` Chen, Kenneth W

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=424DFF88.30003@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@osdl.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