|
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.
Also, the "processor loads" are pretty ridiculous. Running "yes"? That's an IO bound process, I really can't believe that it would strain the processor, and just because you run two instances, how do you know that they're running on separate cores?
Calculating pi is a little better, but you're still really under-utilizing the computers main functional units. You really need a test that does conditional logic, integer arithmetic, floating point, block memory moves, IO, graphics operations, and vector operations all at the same time, AND on both cores simultaneously.
I don't know what that test would even be, it would take some considerable design to do it right; but a high-end game would probably be much, much better than anything you run from a command line.
I think the real lesson learned (confirmed) here, is that there are wide variances in end user results, and there probably isn't one "quick fix" for all users.
|
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.