From: Michael Meyer <mike65134@yahoo.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: performance differences: "maxcpus=1" vs. "echo 0 > /sys/devices/system/cpu/cpu1/online"
Date: Sat, 29 Mar 2008 21:55:19 +0100 (CET) [thread overview]
Message-ID: <954006.94043.qm@web25815.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20080328135946.GB4404@ucw.cz>
--- Pavel Machek <pavel@ucw.cz> schrieb:
> On Tue 2008-03-25 14:47:50, Michael Meyer wrote:
> > Hi,
> >
> > what is the difference between booting a dual core
> > machine with "maxcpus=1" or by deactivating the second
> > core at run time with "echo 0 >
> > /sys/devices/system/cpu/cpu1/online"?
>
> maxcpus=1 : core stays powered off
> 0 > online : core enters halt.
>
> > I observed a funny behaviour of apache ant: although
> > it uses javac which is single threaded, a compile run
> > with "maxcpus=1" is actually faster than a compile run
> > with both cores activated. But with the second core
> > deactivated using "echo 0 >
> > /sys/devices/system/cpu/cpu1/online" it is even slower
> > than with both cores.
>
> Thermal fun? Check cooling.
I have an extremely well cooled case and a Thermaltake Typhoon sitting
on the E6600 (Intel TDP 65 Watt). At a room temperature of 20°C both
cores idle at 21°C and after one hour of two instances of prime95
running they are both at 28-33°C. As the E6600 is specified until 60°C
(I believe), this should prevent any thermal throttling?
> > Is here any method to get the exact same behaviour of
> > "maxcpus=1" with disabling the second core only
> > temporarily? So that the second core could be disabled
> > before the ant execution and enabled after the ant
> > execution?
>
> Patch pushing 0 > online cores into C4 would be nice.
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
E-Mails jetzt auf Ihrem Handy.
www.yahoo.de/go
next prev parent reply other threads:[~2008-03-29 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 13:47 Michael Meyer
2008-03-25 14:08 ` Luciano Rocha
2008-03-25 16:38 ` Michael Meyer
2008-03-25 17:16 ` Andi Kleen
2008-03-25 17:23 ` Michael Meyer
2008-03-25 17:49 ` Wander Winkelhorst
2008-03-25 17:56 ` Michael Meyer
2008-03-25 17:57 ` Andi Kleen
2008-03-25 23:27 ` Len Brown
2008-03-26 7:26 ` Michael Meyer
2008-03-28 14:00 ` Pavel Machek
2008-03-28 13:59 ` Pavel Machek
2008-03-29 20:55 ` Michael Meyer [this message]
2008-03-29 21:22 ` Pavel Machek
2008-03-29 22:16 ` Michael Meyer
2008-04-02 11:31 ` Pavel Machek
2008-03-29 23:22 ` Bernd Eckenfels
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=954006.94043.qm@web25815.mail.ukl.yahoo.com \
--to=mike65134@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®