4 ms·
"Single core performance is still the single most important metric for most users," This is an empty statement backed by no data. The only evidence you provide
by chetanahuja 10y ago
"Single core performance is still the single most important metric for most users,"
This is an empty statement backed by no data. The only evidence you provide to the superiority of single core perf is browser performance. Except,
1) browser usage is now a mostly insignificant part of time spent on mobile (http://flurrymobile.tumblr.com/post/127638842745/seven-years-into-the-mobile-revolution-content-is http://flurrymobile.tumblr.com/post/127638842745/seven-years... )
and
2) The bottleneck in mobile apps which depend on the network (including browsing the web) is rarely the CPU, it's the network.
- acdha 10y agoThat's why I mentioned embedded web views: a lot of time recorded as native apps involves embedded web-views and these days that means things like JavaScript or layout performance matter more than might be immediately obvious. On iOS, the least involved way to see this is in things like news apps where Safari content blockers also block advertisements in the app. The other side of this is that we're not really talking about which app has the most time in the foreground so much as which app causes the user to wait the most. Much of that time will be network I/O which is a real challenge but also not relevant to this discussion about CPU performance. Fundamentally, all I'm trying to say is that Amdahl's law still applies until we're at the point where the user is never waiting on computation. Developers have been getting better at multithreading but uneven CPU usage is still common enough that I'd favor fewer faster cores over more slower cores.