http://www.eso.org/public/archives/images/large/eso1242a.jpg
also, this should be on every retina users wallpaper
also, this should be on every retina users wallpaper
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 tell if you have a strong computer. Also Retina users come in.
- Thread starter InfinitiG
- Start date
- Sort by reaction score
Something is wrong then. My CPU is idle 85% on activity monitor while loading the image. That includes other ACTIVE processes in the background. Base rMBP.
Attachments
lawl something is wrong with your CPU then. I was 85-90% idel. You must have crappy internet.
lol... k then. I have 100Mb internet connection, and i was loading at 50-60KB a second. Safari web content went nuts on the processor but i am not sure why, it is supposedly just downloading a hi res pic? or something? Seems more of a problem with Safari than anything else. or something. what was this thread about anyways??
To those who say 80% idle, that's actually NOT right.
Apparently, Activity Monitor counts 100% CPU utilization as only about 12% on the usage graph. Why? Because the quad-core chip counts as having 8 CPUs (4 actual cores, 8 virtual threads), and since you are only using 100% of 1 of those CPUs, that must be only 12% of your entire capacity.
Makes sense, right? Except that 4 of those "cores" are virtual cores, so you only need to max out 1 real core for things to get totally bogged. See the individual graphs for each core to see how the load is distributed, and how it comes really close to bogging down the cores at some points. It's obvious from the individual core graphs that 80% idle at that point is impossible!
And folks, this is a prime example of what I'd call a CPU-BOUND situation. If your rMBP lags during this time, it's because the CPU core handling the main interface thread is bogged by this silliness.
Thank you, OP... for finding a perfect example for me to show how graphics on the Retina MacBook is NOT dependent on the GPU.
Apparently, Activity Monitor counts 100% CPU utilization as only about 12% on the usage graph. Why? Because the quad-core chip counts as having 8 CPUs (4 actual cores, 8 virtual threads), and since you are only using 100% of 1 of those CPUs, that must be only 12% of your entire capacity.
Makes sense, right? Except that 4 of those "cores" are virtual cores, so you only need to max out 1 real core for things to get totally bogged. See the individual graphs for each core to see how the load is distributed, and how it comes really close to bogging down the cores at some points. It's obvious from the individual core graphs that 80% idle at that point is impossible!
And folks, this is a prime example of what I'd call a CPU-BOUND situation. If your rMBP lags during this time, it's because the CPU core handling the main interface thread is bogged by this silliness.
Thank you, OP... for finding a perfect example for me to show how graphics on the Retina MacBook is NOT dependent on the GPU.
Last edited by a moderator:
All of your CPU percentages added up = 133.8
You have 4 real cores and 4 virtual cores so Activity Monitor thinks you have 8 cores.
800 - 133.8 = 666.2
133.8 / 800 = 16.725
666.2 / 800 = 83.275
I don't understand what you're trying to imply. The screenshot is accurate. Activity Monitor (in this regard anyway) is accurate.
You have 4 real cores and 4 virtual cores so Activity Monitor thinks you have 8 cores.
800 - 133.8 = 666.2
133.8 / 800 = 16.725
666.2 / 800 = 83.275
I don't understand what you're trying to imply. The screenshot is accurate. Activity Monitor (in this regard anyway) is accurate.
To those who say 80% idle, that's actually NOT right.
Apparently, Activity Monitor counts 100% CPU utilization as only about 12% on the usage graph. Why? Because the quad-core chip counts as having 8 CPUs (4 actual cores, 8 virtual threads), and since you are only using 100% of 1 of those CPUs, that must be only 12% of your entire capacity.
Makes sense, right? Except that 4 of those "cores" are virtual cores, so you only need to max out 1 real core for things to get totally bogged. See the individual graphs for each core to see how the load is distributed, and how it comes really close to bogging down the cores at some points. It's obvious from the individual core graphs that 80% idle at that point is impossible!
And folks, this is a prime example of what I'd call a CPU-BOUND situation. If your rMBP lags during this time, it's because the CPU core handling the main interface thread is bogged by this silliness.
Thank you, OP... for finding a perfect example for me to show how graphics on the Retina MacBook is NOT dependent on the GPU.
What I'm trying to imply: % idle overall reported by Activity Monitor is wrong as a metric to consider how much load your processor is under.