From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
xen-devel@lists.xensource.com
Subject: Re: [RFC] Scheduler work, part 1: High-level goals and interface.
Date: Fri, 17 Apr 2009 09:17:29 -0700 [thread overview]
Message-ID: <49E8AB99.5060001@goop.org> (raw)
In-Reply-To: <1cd8b7d4-37bc-41c5-923d-c7bb3f565072@default>
Dan Magenheimer wrote:
> And that's the oversimplification I think. Just
> because Intel provides a rule-of-thumb that the extra
> thread increases performance by 30% doesn't mean that
> it is a good number to choose for scheduling purposes.
>
Actually the 70% was a number I plucked out of the air with no
justification at all.
> I suspect (and maybe this has even already been proven)
> that this varies from 0%-100% depending on the workload,
> and may even vary from *negative* to *more* than 100%.
> (Yes, I understand that i7 is supposed to be better than
> the last round of HT... but is it always better?)
>
The only way to know is by measurement, ideally with some specific
performance counter which tells you what went on in that last
timeslice. But if this is a big issue, you can always disable HT, as
lots of people did the last time around.
J
next prev parent reply other threads:[~2009-04-17 16:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:58 [RFC] Scheduler work, part 1: High-level goals and interface George Dunlap
2009-04-09 18:41 ` Jeremy Fitzhardinge
2009-04-10 0:33 ` Tian, Kevin
2009-04-10 16:15 ` Jeremy Fitzhardinge
2009-04-10 17:16 ` Ian Pratt
2009-04-10 17:19 ` Jeremy Fitzhardinge
2009-04-11 10:00 ` Tian, Kevin
2009-04-15 15:47 ` George Dunlap
2009-04-15 13:54 ` George Dunlap
2009-04-15 16:23 ` Jeremy Fitzhardinge
2009-04-10 17:34 ` Jeremy Fitzhardinge
2009-04-11 9:57 ` Tian, Kevin
2009-04-11 17:11 ` Ian Pratt
2009-04-12 6:27 ` Tian, Kevin
2009-04-11 9:52 ` Tian, Kevin
2009-04-15 15:56 ` George Dunlap
2009-04-16 5:11 ` Tian, Kevin
2009-04-16 10:27 ` George Dunlap
2009-04-16 14:10 ` Dan Magenheimer
2009-04-16 16:32 ` Jeremy Fitzhardinge
2009-04-16 18:20 ` Andrew Lyon
2009-04-16 18:28 ` Jeremy Fitzhardinge
2009-04-17 10:17 ` George Dunlap
2009-04-17 14:13 ` Dan Magenheimer
2009-04-17 14:55 ` Jeremy Fitzhardinge
2009-04-17 15:55 ` Dan Magenheimer
2009-04-17 16:17 ` Jeremy Fitzhardinge [this message]
2009-04-17 16:46 ` Dan Magenheimer
2009-04-17 17:05 ` George Dunlap
2009-04-17 10:02 ` Tian, Kevin
2009-04-15 14:29 ` George Dunlap
2009-04-10 0:15 ` Tian, Kevin
2009-04-15 15:07 ` George Dunlap
2009-04-16 4:58 ` Tian, Kevin
2009-04-10 2:28 ` Zhiyuan Shao
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=49E8AB99.5060001@goop.org \
--to=jeremy@goop.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.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 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.