As expected from a chip with four performance cores. As the new vivo X100 Pro gets into the hands of keen testers, we can finally get an idea of the...
Just recording 4K video majority of phones can’t sustain for few minutes, some do it for only 8 minutes then throttle, there are plenty of things which stress phone hardware.
It is kinda more efficient tho.
Power consumption per clock doesn’t scale linearly.
Splitting a task into two parts and running it on two cores at 2 GHz will consume less power and generate less heat than running it on a single core at 4 GHz.
Its significantly harder to do that programming wise, but performance wise it has its benefits.
It also frees up the main high performance core to focus on more important tasks.
That’s assuming you can split it efficiently without any overhead. It’s not just a problem to be “solved” that devs don’t bother with, a lot of tasks scale poorly across threads even if you successfully multi thread them
What do people do on their phones that pulls stress test power continuously for minutes at a time? That 46% is pretty rough though for sure.
Just recording 4K video majority of phones can’t sustain for few minutes, some do it for only 8 minutes then throttle, there are plenty of things which stress phone hardware.
Many games like PUBG-M are still CPU limited, so maybe that, but yea its probably not an all core load
True. I’d be surprised if it really pushed a lot of cores too, but times are changing in that space.
They really should, it shouldn’t be hard to do considering practically every Android phone released has been 8 core
More cores isn’t necessarily more efficient though. A lot of SOCs would prefer to boost one or two high performance cores
It is kinda more efficient tho.
Power consumption per clock doesn’t scale linearly.
Splitting a task into two parts and running it on two cores at 2 GHz will consume less power and generate less heat than running it on a single core at 4 GHz.
Its significantly harder to do that programming wise, but performance wise it has its benefits.
It also frees up the main high performance core to focus on more important tasks.
That’s assuming you can split it efficiently without any overhead. It’s not just a problem to be “solved” that devs don’t bother with, a lot of tasks scale poorly across threads even if you successfully multi thread them