On my mountain Lion 10.8.4 version the CPU utilization as reported by "activity monitor" showed a result greater than 100%. The TOR Browser went up to 100.9 % CPU with still further applications running. I have enclosed a screen shot of the exceeding utilization below
This is a serious concern because this may mean a hidden process not being properly reported..
Can anyone give a reason for this error?
MacBook Pro, Mac OS X (10.6.8)
What your not getting is that 100% is the maximum. There should be no value higher that 100%. This means the operating is missing assigning or representing processes incorrectly
macfrombrampton wrote:
What your not getting is that 100% is the maximum. There should be no value higher that 100%. This means the operating is missing assigning or representing processes incorrectly
Read this carefully.
100% is not the maximum, if you have a dual core cpu (Core2Duo) 200% is the maximum.if you have a 4 core (i7) then 400% will be the maximum, and so on.
Clear now?
Csound1 wrote:
macfrombrampton wrote:
What your not getting is that 100% is the maximum. There should be no value higher that 100%. This means the operating is missing assigning or representing processes incorrectly
Read this carefully.
100% is not the maximum, if you have a dual core cpu (Core2Duo) 200% is the maximum.if you have a 4 core (i7) then 400% will be the maximum, and so on.
Clear now?
You forgot about hyper-threading. My 2011 i7 4 core iMac maximum is 800%. Fours cores and 4 virtual cores...
So, if I had a process using 100% it would only be 12.5% of my total processing power. Which is a lot if the computer is idling.
Yup, and more is possible.
I know that it's so. But let me say, this is a very strange concept.
The percentage is a value that indicate a portion of a whole thing, in this case is the processor.
100% of a CPU is ALL the CPU, even if is a multicore CPU. If you use a whole core of a dual core CPU, you use the 50% of the CPU, not the 100%!
Using 200% of a resource is a nonsense, you need two times the single resource.
The error, imho, is that the label is "%CPU" and should be "% core" instead.
CPU process over 100% usage
