3 ms·
Other ARM SoC's haven't been able to bridge the relative gap in raw single-core performance going on 5+ years, and haven't hit multi parity since iDevices went
by npunt 8y ago
Other ARM SoC's haven't been able to bridge the relative gap in raw single-core performance going on 5+ years, and haven't hit multi parity since iDevices went beyond 2 cores. I don't really see a gamble here at all - adding ML blocks is relatively cheap and icing on the cake.
Take Geekbench (and any other benchmarks) with a grain of salt of course, but benchmarks & reviews all corroborate the same story. See these GB4 results for instance:
Android [1] - 3323 single, 8894 multi
iPhone XS [2] - 4794 single, 11151 multi
Especially for single-core, the latest, fastest Android phone (Galaxy S9) is a bit slower than the iPhone 7 [3], and every other Android phone (running Qualcomm's latest Snapdragon 845) is equivalent to the iPhone 6s / SE. The delta is just huge.
It's actually a structural / incentive problem that keeps Apple at an advantage in this case, so I wouldn't count on the gap being bridged or even reduced anytime soon. Apple has built an incredible flywheel that lets them earn much more $ per chip than Qualcomm or Samsung by bundling them into super high-margin, high-volume iPhones.
Everything equal, my wild-ass guess is Apple can probably throw at least 33% more transistors at workloads than the competition, due to being on leading edge nodes, being comfortable with lower yields, running multiple chip teams in parallel for maximum efficiency & manual layout, etc. This means huge caches, fancy pipelines, lots and lots of specialized silicon, etc. They also have arguably the most talented chip team in the industry.
And that's just the chip. Because Apple is so vertically integrated, they're better able to optimize the device as a whole. That means more expensive components like faster ram & disk, better integration between IP blocks like CPU/GPU/ML, and more optimized OS/drivers that all play into overall performance and differentiated use cases. It's a business structure that is nearly impossible to replicate and will continue to create a lasting advantage.
With regard to how ML is used, it fits the approach Apple is taking to keep things on-device (vs in the cloud) as much as possible. So any use cases where ML is used in the cloud are potential use cases for ML on the device.
[1] https://browser.geekbench.com/android-benchmarks https://browser.geekbench.com/android-benchmarks
[2] https://browser.geekbench.com/ios_devices/56 https://browser.geekbench.com/ios_devices/56
[3] https://browser.geekbench.com/ios-benchmarks https://browser.geekbench.com/ios-benchmarks
- jamesonthecrow 8y agoYour point about the integration between software and hardware is spot on. Even the Android devices with powerful GPUs or AI accelerators are really difficult to access because Android APIs (even the NNAPI) is really tough to use. Core ML "just works" with the CPU / GPU / Neural Engine.
- MBCook 8y agoQualcomm can DESIGN a chip and HOPE it’ll go in 20 million devices in a year. If they take big enough risks it’s possible no one buys the chip and they just eat a huge loss. I do the phone manufacturers don’t want it, or they don’t think it’s worth the extra three dollars compared to a previous chip. Apple has inly one customer, they can design a trip and KNOW it’s going into 150 million devices within a year. Even if the APIs aren’t given to third parties, it may still be a big win for them.
- fisherjeff 8y agoI, too, just ended up on the Geekbench browser and hadn't noticed until now that A12 would appear to be roughly at single-core parity with Kaby Lake-U: i7-8559U: 1901/GHz [0] A12 Bionic: 1998/GHz [1] I'm not familiar enough with the actual tests to know how comparable those scores are, plus, as you say, grain of salt, etc., but the rate at which the gap has been closed continues to be remarkable. [0] https://browser.geekbench.com/macs/433 https://browser.geekbench.com/macs/433 [1] https://browser.geekbench.com/ios_devices/56 https://browser.geekbench.com/ios_devices/56