Re:What I learned from watching my iPad's slow death
by cm2187 on Tuesday February 06, 2018 @05:50PM
(#16320691)
But it's largely because today's improvements have gone into lower CPU consumption than core count. But it could have gone core count, it just 99% of users wouldn't know what to do with more cores and would rather take the battery life.
[ Parent
| on HN ]
Re:What I learned from watching my iPad's slow death
by romwell on Tuesday February 06, 2018 @10:27PM
(#16322040)
>it just 99% of programmers wouldn't know what to do with more cores
Fixed that for you. Remember that every time you experience an unresponsive GUI anywhere, and that's the easy case.
Beyond that, parallelization is generally not easy.
Re:What I learned from watching my iPad's slow death
by cm2187 on Wednesday February 07, 2018 @03:04AM
(#16322922)
I think the vast majority of the time unresponsive GUI are because of blocking network or IO calls. A faster CPU won't do anything. I rarely max out my CPU.
Re:What I learned from watching my iPad's slow death
by 14113 on Wednesday February 07, 2018 @06:19AM
(#16323709)
A UI shouldn't be unresponsive in that case. It should present a progress bar, or other visual indicator that the UI [thread/actor/process] is waiting for the IO [thread/actor/process]. A UI should only become unresponsive when only one [thread/actor/process] is trying to do everything (I.e. both IO and UI), which should only occur if your application is not written with concurrency in mind.
Re:What I learned from watching my iPad's slow death
by Const-me on Wednesday February 07, 2018 @01:45PM
(#16326933)
Mobile SoCs still increase core count but it doesn’t need to increase power consumption.
E.g. Qualcomm SDM845 has 8 cores in total, 4 faster ones that are only used rarely, and 4 power efficient ones.
Also they offload increasing amount of work from less power efficient general-purpose CPUs to other on-chip hardware, DSPs (for many years), and now GPUs (marketing folks call them neural engines or AI chips).