Linked by Thom Holwerda on Mon 19th Sep 2016 14:58 UTC
Apple

Oh, benchmarks.

Benchmarks of computer hardware have their uses. Especially if you have a relatively narrow and well-defined set of calculations that you need to perform, benchmarks are great tools to figure out which processor or graphics chip or whatever will deliver the best performance - scientific calculations, graphics processing (e.g. video games), these are all use cases where comparisons between benchmarks of different hardware components can yield useful information.

A different way to put it: benchmarks make sense in a situation where "more power" equals "better results" - better results that are noticable and make a difference. A GTX 1080 will result in better framerates than a GTX 1070 in a modern game like The Witcher 3, because we've not yet hit any (theoretical) framerate limit for that game. A possible future GTX 1090 will most likely yield even better framerates still.

Where benchmarks start to fall apart, however, is in use cases where "more power" does not equal "better results". Modern smartphones are a perfect example of this. Our current crop of smartphones is so powerful, that adding faster processors does not produce any better results for the kinds of ways in which we use these devices. Twitter isn't going to open or load any faster when you add a few hundred megahertz.

In other words, modern smartphones have bottlenecks, but the processor or RAM certainly isn't one of them. Before you can even reach the full potential of your quad-core 2.4Ghz 6GB RAM phone, your battery will run out (or explode), or your network connection will be slow or non-existent.

As a result, I never cared much for benchmarking smartphones. In 2013, in the wake of Samsung cheating in benchmarks, I wrote that "if you buy a phone based on silly artificial benchmark scores, you deserve to be cheated", and today, now that Apple is leading (in one subset of processor) benchmarks with its latest crop of mobile processors, the same still applies.

So when John Gruber posted about Apple A10 Fusion benchmarks...

Looking at Geekbench's results browser for Android devices, there are a handful of phones in shouting distance of the iPhone 7 for multi-core performance, but Apple's A10 Fusion scores double on single-core.

...I snarked:

Funny how just like in the PPC days, benchmarks only start mattering when they favour [insert platform of choice].

Setting aside the validity of Geekbench (Linus Torvalds has an opinion!), this seems to be the usual pointless outcome of these penis-measuring contests: when the benchmarks favour you, benchmarks are important and crucial and the ultimate quanitification of greatness. When the benchmarks don't favour you, they are meaningless and pointless and the world's worst yardsticks of greatness. Anywhere in between, and you selectively pick and choose the benchmarks that make you look best.

I didn't refer to Apple's PowerPC days for nothing. Back then, Apple knew it was using processors with terrible performance and energy requirements, but still had to somehow convince the masses that PowerPC was better faster stronger than x86; claims which Apple itself exposed - overnight - as flat-out lies when the company switched to Intel.

When I use my Nexus 6P and iPhone 6S side-by-side, my Nexus 6P feels a lot faster, even though benchmarks supposedly say it has a crappier processor and a slower operating system. Applications and operations seem equally fast to me, but Android makes everything feel faster because it has far superior ways of dealing with and switching between multiple applications, thanks to the pervasiveness of activities and intents or the ability to set your own default applications.

Trying to quantify something as elusive and personal as user experience by crowing about the single-thread performance of the processor it runs on is like trying to buy a family car based on its top speed. My 2009 Volvo S80's 2.5L straight-5 may propel the car to a maximum speed of 230km/h, but I'm much more interested in how comfortable the seats are, all the comfort options it has, if it looks good (it does), and so on. Those are the actual things that matter, because the likelihood of ever even approaching that 230km/h is very slim, at best.

I bought an iPhone 6S and Apple Watch late last year and used them for six months because I feel that as someone who writes about every platform under the sun, I should be using them as much as (financially and practically) possible. I used the iPhone 6S as my only smartphone for six months, but after six months of fighting iOS and Apple every step of the way, every single day, I got fed up and bought the Nexus 6P on impulse.

Not once during those six months did I think to myself "if only this processor was 500Mhz faster" or "if only this thing had 4GB of RAM". No; I was thinking "why can't I set my own default applications, because Apple's are garbage" or "why is deep linking/inter-application communication non-existent, unreliable, broken, and restricted to first-party applications?" or "why is every application a visual and behavioural island with zero attention to consistency?".

iOS could be running on a quantum computer from Urbana, Illinois, and it wouldn't solve any of those problems.

The funny thing is - Gruber actually agrees with me:

I like reading/following Holwerda, because he's someone who I feel keeps me on my toes. But he's off-base here. I'm certainly not saying that CPU or GPU performance is a primary reason why anyone should buy an iPhone instead of an Android phone. In fact, I'll emphasize that if the tables were turned and it were Android phones that were registering Geekbench scores double those of the iPhone, I would still be using an iPhone. In the same way that I've been using Macs, non-stop, since I first purchased a computer in 1991. Most of the years from 1991 until the switch to Intel CPUs in 2007, the Mac was behind PCs in performance. I never argued then that performance didn't matter - only that for me, personally, the other benefits of using a Mac (the UI design of the system, the quality of the third-party apps, the build quality of the hardware, etc.) outweighed the performance penalty Macs suffered. The same would be true today if Apple's A-series chips were slower than Qualcomm's CPUs for Android.

So, he'd be buying iPhone even if the benchmark tables were turned, thereby agreeing with me that when it comes to phones, benchmarks are entirely meaningless. Nobody buys a smartphone based on processor benchmark scores; at this point in time, people mostly buy smartphones based on the smartphone they currently have (i.e., what platform they are currently using) and price.




That being said, there is one reason why benchmarks of Apple's latest mobile processors are quite interesting: Apple's inevitable upcoming laptop and desktop switchover to its own processors. OS X (or macOS or whatever) has been in maintenance mode ever since the release and success of the iPhone, and by now it's clear that Apple is going to retire OS X in favour of a souped-up iOS over the coming five years.

I know a lot of people still aren't seeing the forest through the trees on this one, but you can expect the first "iOS" MacBook within 1-2 years. I put iOS between quotation marks because that brand of iOS won't be the iOS you have on your phone today, but a more capable, expanded version of it.

Vlad Savov:

It sounds wild, but the A10 looks to have the power and efficiency to handle the workload of a full PC. This coalescence of mobile and desktop PCs is driven by forces on both sides: mobile chips are getting more potent at the same time as our power needs are shrinking and our tasks become more mobile. If you think your workplace isn't changing much because there are a bunch of weathered Dell workstations sitting next to frumpy HP printers, consider just how much more work every one of your officemates is doing outside the office, on their phone. And all those grand and power-hungry x86 applications that might have kept people running macOS - Adobe's Photoshop and Lightroom being two key examples - well, they're being ported to iOS in almost their full functionality, having been incentivized by the existence of Apple's iPad Pro line, last year's harbinger for this year's performance jump.

Unlike Windows, whose x86 reliance is tied to its dominance of the lucrative PC gaming market, Apple really has very few anchors locking it down to macOS. The Cupertino company has been investing the vast majority of its development time into the mobile iOS for years now, and that shows in the different rates of progress between its two pieces of software. macOS is, in many ways, legacy software just waiting for the right moment to be deprecated. It’s getting a fresh lick of paint now and then, but most of its novelties now relate to how it links back to Apple's core iOS and iPhone business.

This is where benchmarking and the performance of Apple's A10 Fusion processor do come into play, because even in the constrained environment of a smartphone, it seems to be reaching performance levels of laptop and desktop processors.

That "iOS" MacBook is closer than you think.

Thread beginning with comment 634612
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Reason to buy a new phone
by Gargyle on Tue 20th Sep 2016 12:17 UTC in reply to "Reason to buy a new phone"
Gargyle
Member since:
2015-03-27

[...] and having the 200GB SD card in gives me a lot of space for big things I store. [...]

How does that work out for you? Did you format the card in something other than FAT32? I wonder because that card would unlock the potential for a very big mobile video library, but since FAT32 cannot handle files larger than 2GiB the point is moot.

I never tried anything to test whether my phone support any other file system than FAT32 on the SDcard. If it would, that would be great!

I also wonder if TWRP and other recoveries are able to cope with the unexpected file system on such an SDcard.

Reply Parent Score: 1

RE[2]: Reason to buy a new phone
by jbauer on Tue 20th Sep 2016 12:22 in reply to "RE: Reason to buy a new phone"
jbauer Member since:
2005-07-06

"[...] and having the 200GB SD card in gives me a lot of space for big things I store. [...]

How does that work out for you? Did you format the card in something other than FAT32? I wonder because that card would unlock the potential for a very big mobile video library, but since FAT32 cannot handle files larger than 2GiB the point is moot.

I never tried anything to test whether my phone support any other file system than FAT32 on the SDcard. If it would, that would be great!

I also wonder if TWRP and other recoveries are able to cope with the unexpected file system on such an SDcard.
"

It should support exFAT. My two-year old Samsung tablet does.

Reply Parent Score: 2

darknexus Member since:
2008-07-15

Probably ExFAT, though it's usually reasonable that Android supports EXT4 as well (though whether Samsung fscked that up is anyone's guess). In either case though, FAT32 is by no means required anymore, thank goodness.

Reply Parent Score: 2

lancealot Member since:
2007-02-25

"[...] and having the 200GB SD card in gives me a lot of space for big things I store. [...]

How does that work out for you? Did you format the card in something other than FAT32? I wonder because that card would unlock the potential for a very big mobile video library, but since FAT32 cannot handle files larger than 2GiB the point is moot.

I never tried anything to test whether my phone support any other file system than FAT32 on the SDcard. If it would, that would be great!

I also wonder if TWRP and other recoveries are able to cope with the unexpected file system on such an SDcard.
"

It works great for storing large data, which is exactly what you want to use it for. Recording in Hi-Def can create large files very quickly. As other people said Samsung (some phones might only support lower capacity SDs with FAT/32) uses ExFAT so you don't hit that 4GB file size limit of FAT32, as the max file size limit for ExFAT is 16 EB (good luck find a SD card that size LOL). I personally store my emulator ROMS, downloaded offline maps, large games, images, videos, offline Spotify downloads, language downloads, etc.. All of those would take a considerable amount of storage away from the 32GIG the phone comes with (for a US based Samsung S7). You also have the ability to move some apps (if they allow it) to the SD. Most games do allow this which are mostly the the apps using the largest app storage. Then of course some apps allow you to pick where to store large downloaded data, such as Here Maps allowing you to pick where to download the offline maps to.

If you want the ability to pop out the SD and mount it on another device and put it back in the phone, be sure not to use Android adaptive storage or encrypt the SD card. Adaptive Storage is not an issue with the S7 since Samsung disabled the ability to turn this on (which I can see reasoning beyond doing this). I know some peoples concern is peoples ability to access the SD if it is not encrypted. That is why you store only stuff your less worried about having on the SD. If you are worried about having your phone pictures and video on a unencrypted SD, then store them on the local phone storage which is encrypted. If you don't want to mount the SD on other devices, then encrypt the SD. Having a choice is nice.

Edited 2016-09-21 00:00 UTC

Reply Parent Score: 1