Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to turn off a core?
- Thread starter squwish
- Start date
- Sort by reaction score
Actually, there is a tool in the developer tools that can turn off a core, but it's not something that just happened to your mac by accident.
Are you using Handbrake? I was under the impression that the current release version has some limitations that are being worked on regarding performance on multiple cores. There are threads about this here, I think. Before you conclude that a core is off (which I would think something like iStat can tell you pretty easily), I would also look at threads related to speed on the app you're using and how well that app handles multiple cores.
Are you using Handbrake? I was under the impression that the current release version has some limitations that are being worked on regarding performance on multiple cores. There are threads about this here, I think. Before you conclude that a core is off (which I would think something like iStat can tell you pretty easily), I would also look at threads related to speed on the app you're using and how well that app handles multiple cores.
yeah, see when I look at iStat, it only shows the temp for CPU A. I am not using hand break but I use Final Cut Studio 2 for rendering film.
iStat will only give you one temperature because the C2D chips only have one temperature sensor.
As for speed, have you tried looking at your processes in Activity Monitor? When your Mac gets slow, have a quick check on your processes/pageins/pageouts to see if there's anything unsuspected there.
There is this program called UnrarX which is running in the background( at 98%) I found the problem.
thanks
Sorry, iStat was a bad example. You're correct, the cpu temps tell you nothing. I was thinking of the activity component of it. Probably the easiest way is to open activity monitor, run *several* apps that consume significant resources, and watch where the (total) CPU allocation goes. If it adds up to more than 1.0 / 100%, both cores are working. That way does work, doesn't it?
that does make sense but that means that 200% = 2 cores? wait, I'm lost.
That's exactly right; 100% CPU usage is a single core.
You shouldn't necessarily expect 200% utilization, however, unless you're either using a program that's very good at multi-core usage, or running several programs that can be assigned to different cores. But it should be well above 100.
