| Article: |
MacBook Pro: The Thermal Paste Question | |
| Subject: | Just more anecdotal evidence | |
| Date: | 2006-05-25 15:24:06 | |
| From: | OReillyAnon | |
|
Given the lack of scientific rigor here, i.e. no true control group, dubious measurement tools, etc., this can only be regarded as more anecdotal evidence thrown onto the pile. This doesn't disprove the theory that there is a problem with thermal paste application.
|
||
Showing messages 1 through 2 of 2.
-
Just more anecdotal evidence
2006-05-25 21:08:50 James Duncan Davidson |
[View]
-
Just more anecdotal evidence
2006-05-25 20:15:42 allenmurdock [View]
Try running Activity Monitor, then run "yes > /dev/null" in two separate Terminal windows. You'll discover that both CPUs will immediately be pinned at 100%. Just thought I'd point that out.



And, if you don't beleive that running `yes` in two windows won't zip up your cpu temps, do it while leaving a MacBook Pro in your lap. Give it just a few minutes and you'll have a problem. :) That's a simple one to test. I'm sure other ways of loading the processor might heat the processor more--at least it would flip more gates on and off--but, it my case and that of lots of others, the load `yes` puts on is more than enough.
As far as verifying both cores are loaded, you can watch Activity Monitor or use the CPU pref panel that comes with the CHUD tools.
As far as your conclusion, yes I'd agree that the lesson is that there are no quick fixes. But I also come back to my original conclusion that I think the real fix is for just a bit more fan to be applied to the equation during normal usage. That was my big takeaway.