8 ms·
Observing the A11's Heterogenous Cores
- bipson 9y agoIs the author seriously so deep in the "Apple-is-the-world" bubble that he has not yet heard of BigLittle? In what way is the A11 different?
- wyldfire 9y agoIndeed, other big.LITTLE like designs are out there besides the A11. But the article isn't strictly focused on "Apple is a superior innovator." > My theory was that this should show a strongly bimodal distribution of running times on the A11. ...and then he proceeds to devise a test. This is ultimately how you might verify the functionality of the hardware and the Darwin scheduler. If it were naive, the test might not have behaved this way. BTW if anyone wants to do similar experimentation with a MUCH cheaper target, you can use the ODROID Xu4 (Exynos 5422, < 100 USD).
- haikuginger 9y agoI'm not familiar with the current state of bigLITTLE, but at least initially, bigLITTLE clusters weren't capable of heterogeneous compute; you could shift between cache-coherent clusters (use either all four big cores or all four LITTLE cores) or have virtual cores, each made up of one big and one LITTLE core, with the kernel managing which physical core was actually executing threads assigned to the logical core. My understanding of the A11 is that it's fully heterogeneous with the capability to run and assign code across any permutation of its physical cores.
- zeusk 9y agoheterogeneous big.LITTLE implementations are in consumer android devices since late 2013s.
- ksk 9y ago>Is the author seriously so deep in the "Apple-is-the-world" bubble that he has not yet heard of BigLittle? Why the rude comment?
- ajross 9y agoIn this case it's probably genuine surprise. The ARM big.LITTLE trick (see https://en.wikipedia.org/wiki/ARM_big.LITTLE https://en.wikipedia.org/wiki/ARM_big.LITTLE) been workable and shipping on real devices for half a decade now[1]. This is not particularly innovative ground, and to write a whole blog post without even mentioning the fact or doing a comparison with any of the existing devices implies that maybe the author didn't do enough research. Whether that's worth being "rude" or not is an exercise for the reader. [1] Edit to add: and producing fairly "meh" results as far as power consumption goes vs. their more conventional quad-core competitors. Honestly it's not impossible that Apple found some tricks to exploit here that the other SoC vendors haven't, but this post didn't find them.
- ksk 9y ago>This is not particularly innovative ground, and to write a whole blog post without even mentioning the fact or doing a comparison with any of the existing devices implies that maybe the author didn't do enough research. The blog context is made clear in the second sentence "With the release of the iPhone X, I set out to see if I could observe these heterogeneous cores in action.". If the context was "Here is the current state of heterogeneous computing on mobile devices", you might have a point. As to whether its innovative or not, Surely, you agree that designing a chip is more than just the bumper sticker definition of "it has cores with different speeds". But maybe you're right and it isn't innovative at all. It would be interesting to find out. >This is not particularly innovative ground, and to write a whole blog post without even mentioning the fact or doing a comparison with any of the existing devices implies that maybe the author didn't do enough research. I don't think it implies that at all. If a C++ dev is excited about a new C++ feature and writes an article, it doesn't mean they're automatically ignorant about other languages that already have this feature.
- jws 9y ago
- purell_hack 9y agoI got two paragraphs in and said, out loud, "Are you kidding me" because of how masturbatory (for lack of a better term) it reads as. bigLITTLE has been _shipping_ since at least 2013. https://en.wikipedia.org/wiki/ARM_big.LITTLE#Implementations https://en.wikipedia.org/wiki/ARM_big.LITTLE#Implementations
- wolf550e 9y agoWikipedia says [1] that ARM big.LITTLE "Heterogeneous Multi-Processing (HMP), which enables the use of all physical cores at the same time" has been "implemented in the Samsung Exynos starting with the Exynos 5 Octa series (5420, 5422, 5430)", available in Q3 2013. 1 - https://en.wikipedia.org/wiki/ARM_big.LITTLE#Heterogeneous_multi-processing_.28global_task_scheduling.29 https://en.wikipedia.org/wiki/ARM_big.LITTLE#Heterogeneous_m...
- tasty_freeze 9y agoI think the original article is fine as it is and has no need to cite everything which came before. But I wanted to point out that Nvidia Tegra3 shipped with big/little in 2011: https://www.cnet.com/news/nvidias-tegra-3-cpu-increases-performance-while-saving-power/ https://www.cnet.com/news/nvidias-tegra-3-cpu-increases-perf...
- pohl 9y agoI couldn't find any quote in the article that supports the suggestion that the author isn't/wasn't unaware of big.LITTLE. Could you cite one that supports your snark?
- mikeash 9y agoIt's an Apple-focused blog. The A11 may not be doing anything new when considering the wider world, but it's the first Apple CPU to have it. Do not confuse "I did not mention this other thing that is not entirely off topic" with "I was not aware of this other thing."
- valuearb 9y agoWell, it's benchmarks are different. It's crushing all the other mobile processors.
- deleted 9y ago[deleted]
- oflannabhra 9y agoI didn't see the author present any technology as being novel industry-wide. He did present big.LITTLE architecture as novel to the Apple and iOS ecosystems, which is correct.
- pmattos 9y agoIn no way the author — a vey respected engineer in the Apple community BTW — pretended to provide an exhaustive overview of the multi-core heterogeneous computing world (or assert that Apple invented all this tech on its own). I honestly think that he just wanted to provide a very brief comparison between A10 and the latest A11, and then go on with his article core subject ;)
- Moto7451 9y agoUnless he edited the post after you commented, I don’t quite agree with the comparison. He states “in the Apple world” as a qualifier to his history lesson. He doesn’t say “Apple invented multi core CPUs” or “Apple had multi core CPUs first”.
- mikeash 9y agoThe only edit I've made so far was to correct a massive brain fart in my summary of the cluster means at the end. People just can't handle a focused post, apparently.
- mikeash 9y ago> But he described the Apple ecosystem as if nothing outside it even exists. I did no such thing. I focused on Apple because my blog focuses on Apple, but at no point did I state or imply that nothing outside of Apple exists. I even went out of my way to say that multicore systems have "become the norm in many parts of the computing world."
- macintux 9y ago
- dep_b 9y agoA significant part of the people that respond here seem to be offended by the lack of acknowledgement for the fact that Samsung had this before Apple had it. I find that a really interesting response from a psychological standpoint. Not the fact that the article could mention it although for the topic at hand it's not required, but just the fact that it actually is offensive to some people. All I see is an Apple geek dissecting his new Apple toy and comparing it to his previous Apple toys and having a good time exploring it's capabilities. I wish I could read more stuff that goes a bit deeper like this.
- GeekyBear 9y agoI've always found this experiment to be revealing: >Specifically, after explaining briefly that I was the editor of a tech news site, I would ask iPhone users “why do you use an iPhone?” and Android phone users “why do you use an Android phone?” My phone was always in my pocket when I asked, and I made sure to never mention a rival platform at all. In about three months I ended up asking 219 different people this question, including 112 iPhone users and 107 Android users. I wasn’t terribly concerned with the features of each platform that people liked most. I just wanted to see how many people, unprovoked, would mention a rival platform in a negative way when offering their responses to a complete stranger. http://bgr.com/2016/10/25/iphone-vs-android-survey-takeaways/ http://bgr.com/2016/10/25/iphone-vs-android-survey-takeaways...
- pohl 9y agoThank you for sharing. Here's the tl;dr: 47% of Android users sampled (51 out of 107) « said things like “iPhone users are a cult,” “I hate Apple,” “only stupid people use iPhones,” or “I hate the iPhone” when explaining to me why they chose an Android device. Seriously, people actually used the word hate » 5% of iPhone users sampled (6 out of 112) « said something negative about Android or about a specific Android phone manufacturer. Not a single person make a negative blanket statement about Android users in general. »
- bipson 9y agoYet anyone that is commenting something on this thread which could be interpreted as anti-Apple is downvoted quite harshly.
- my123 9y agoBig.little was popular on ARM land before too, the Apple difference is the speed of the big cores, and plain higher clockspeeds...
- StillBored 9y agoI'm not sure all this big.little stuff is the future. The heterogenous cores make scheduling/caching/etc a nightmare particularly when someone decides that the cores have different features. Particularly, since I think its all a crutch for lack of finer grained power control within the CPU core. Want to save more power, turn off a few of the duplicate functional units, shutdown 3/4 of the ROB buffer, or fuse a few pipeline stages together as the frequency is reduced. Whatever. The point being its possible to have a finer grained performance profile on a bunch of higher performance cores rather than wasting 1/2 the die on caches and cores that are basically useless for any real work outside of handling idle loop wakeup events to tell the GPU it needs to scroll or run a idle TCP stack's keepalives..
- lathiat 9y agoAs someone relatively naive on these things, iOS seems like the kind of platform where it's easier to integrate than the more generic case. Much easier for them to optimise for it, since (1) Apps are often using Apple-provided frameworks and you can optimise around those specifically (2) iPhones are generally performing a single task in the foreground and frequently background tasks. Even with an iPad that moves up to only 2 simultaneous tasks. Seems much easier to optimise the scheduling based on that. (3) There is a very limited set of hardware developers have to optimise for, literally basically 1 CPU per year. On that basis, any quirks will likely be found in development and can be fixed then rather than having different quirks accross a wider range of CPUs that you might have seen in Android [since 1 and 2 would apply reasonably equally to Android devices]
- gok 9y agoEven SMP chips today don't make scheduling particularly easy. Some cores share caches and some don't, some are on different sockets, some don't share the same memory banks, some are clock boosted or down clocked...
- gumby 9y agoI disagree: we've been playing these games for a long time and I don't see anything on the horizon. You know how you start a phone call in Japan with Moshi moshi‡? In the 1990s the software in some of the PHS phones would wait until there was enough energy coming through the microphone before powering up the compression hardware in order to save just a little more power. So the "Moshi moshi" would get cut off. Basically anything to save power -- people hate recharging. ‡ It's like the linguistic equivalent of the old TTY STX (which still survives in ASCII!)