8 ms·
Qualcomm Insider: Apple 64-Bit Chip `Hit Us in the Gut'
- data-cat 13y agoThis makes me wonder when 128 bit processing will come around.
- wmf 13y agoAs soon as you can put 2^64 bytes of RAM in a PC, I guess.
- codeflo 13y agoWe already have 128-bit registers for vector computations (for example, the SSE registers in x86). As for addressing 128 bits of memory: that's more than a century off even if memory continues to double every two years (which doesn't seem likely to begin with). It's actually plausible that the step to 64-bit addressing was the last one, ever.
- dragontamer 13y ago64-bit ARM means passing around 64-bit pointers by default. In most code settings, this pollutes the cache (you can only hold half as many pointers), and leads to slightly weaker performance. 64-bit computing is NOT an advantage in the phone world. It is a massive advantage for database applications or large web services... but certainly not for phone apps in the near future.
- codeflo 13y agoI know what 64-bit computing is. And I didn't say anything about phone chips, or ARM. It seems like you're posting this rant to every subthread, regardless of content?
- data-cat 13y agoThat is an interesting conclusion. I did not realize x86 already had 128 bit registers. That was really what I was referring to. We might not need to worry about addressing more memory yet but I feel like larger registers will still be useful.
- stephencanon 13y agoActually, x86 already has 256-bit vector registers (AVX), and will have 512-bit vector registers in a few years (AVX-512). If you include the exotic-but-still-x86-based xeon phi it already has 512-bit vector registers.
- colanderman 13y agoDon't know why you were downvoted. Modern x86 chips not only have 128-bit vector registers, but also 256-bit ones: http://en.wikipedia.org/wiki/Advanced_Vector_Extensions http://en.wikipedia.org/wiki/Advanced_Vector_Extensions (And while one could argue that a vector register isn't a "real" general-purpose register, the primary difference is that you can't perform fullwidth arithmetic, which is of very little use > 64 bits anyway.)
- dragontamer 13y agoYour comment made me lol. +1, easily. No seriously, there is little to no speed difference in 32-bit vs 64-bit computing. The REAL benefit is the ability to address memory beyond 4GBs. But even the most high-end phones are stuck with 2GB... hell, a number of laptops are still shipping with 2GB of RAM. Let alone phones. The 64-bit "advantage" is almost entirely a marketing gimmick. That said, it is a known fact that Apple's iPhone chip is leagues ahead of its competitors in terms of performance / watt. Qualcomm has a value buy with Snapdragon and their integrated LTE chip + FCC conformance. But Apple has full integration, and controls the software / hardware from bottom up. That is a real advantage that is leading to improved battery lives and faster performance. (This is less an "Apple Advantage" and more of an "Android disadvantage". Android should be able to catch up if they got their act together... but the reliance on Dalvik-VM code and unoptimized APIs leads to noticeably worse battery life) Beyond that, Apple is beginning to invest into state-of-the-art foundries, possibly to create chips in house by the year 2016 or 2017. They've also bought out the high-end 20nm wafers through 2014, forcing their competitors to lag behind on the older 28nm process nodes. (Hell, even AMD / NVidia are feeling the sting. All AMD / NVidia roadmaps to better GPUs are at 28nm technology... Only Intel: who has reached 14nm on their in-house labs, remains unaffected by Apple's purchasing power) When your company has $100 Billion in cash, you can afford to have a process node advantage over your opponents.
- wsc981 13y ago> "Beyond that, Apple is beginning to invest into state-of-the-art foundries, possibly to create chips in house by the year 2016 or 2017. They've also bought out the high-end 20nm wafers through 2014, forcing their competitors to lag behind on the older 28nm process nodes. (Hell, even AMD / NVidia are feeling the sting. All AMD / NVidia roadmaps to better GPUs are at 28nm technology... Only Intel: who has reached 14nm on their in-house labs, remains unaffected by Apple's purchasing power)" Very interesting. Would you have a source? I know Apple did the same "trick" with touch screens when the iPhone was introduced. I think these actions are typical of Cook - from what I understand he was earlier (before he became CEO) responsible for the whole inventory chain management and it's likely an area he's still involved in.
- 13y ago
- nradov 13y agoIBM System i (AS/400) servers have supported 128 bit pointers for decades.
- colanderman 13y agoNice. I suppose this is for memory-mapped file I/O? Or do those beasts really have access to terabytes of core? (In which case I will become jealous of my dad, who works with AS/400s.)
- nradov 13y agoThe former. They don't support any more physical memory than other high-end servers.
- wnevets 13y ago"says the Qualcomm employee." sounds legit to me.
- guttermaw 13y agoTim Cook should do the next keynote in an invisible nano-robe. The whole industry will be naked in a week.
- wmf 13y agoTo be fair, iOS is getting performance improvements from ARMv8. That leaves me with the question of whether such improvements apply to non-ObjC code and if so why the rest of the industry didn't realize that.
- danielsju6 13y agoObjective-C has some really interested 64-bit tricks, here's a great blog post on the changes and how they affect things https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-yo...
- WalterSear 13y agoExcept that 64 bits is still nothing but a marketing gimmick as far as the memory sizes in smart phones is concerned. All those companies are panicking, not because they are being left behind technologically, but they are being left behind in the buzzword war.
- AlexanderDhoore 13y ago"The "64-bit" A7 is not just a marketing gimmic, but neither is it an amazing breakthrough that enables a new class of applications. The truth, as happens often, lies in between. The simple fact of moving to 64-bit does little. It makes for slightly faster computations in some cases, somewhat higher memory usage for most programs, and makes certain programming techniques more viable. Overall, it's not hugely significant. The ARM architecture changed a bunch of other things in its transition to 64-bit. An increased number of registers and a revised, streamlined instruction set make for a nice performance gain over 32-bit ARM. Apple took advantage of the transition to make some changes of their own. The biggest change is an inline retain count, which eliminates the need to perform a costly hash table lookup for retain and release operations in the common case. Since those operations are so common in most Objective-C code, this is a big win. Per-object resource cleanup flags make object deallocation quite a bit faster in certain cases. All in all, the cost of creating and destroying an object is roughly cut in half. Tagged pointers also make for a nice performance win as well as reduced memory use." [1] https://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html https://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-an...
- makomk 13y agoSo basically, it's only really a substantial performance win because of a quirk of how Apple's 32-bit code was written, a quirk that doesn't apply to competing platforms.
- chaostheory 13y agoIt will apply to competing platforms in about two years, when the first set of devices with 4 GB or more RAM start appearing.
- ramsaysnuuhh 13y agoCan anyone explain to me why being 64 bit matters on a phone?
- gnator 13y agoI don't think 64 bits matters yet however Apple knows that people will want this 64bit magical thing forcing their competition to follow suit
- danielsju6 13y agoHere's a great blog post on the matter https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-yo...
- leejoramo 13y agoThis story did a good job of explaining the advantages and disadvantages of Apple's 64-bit chip. There are advantages of 32 more bits, but that is only a part of the story. https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html https://mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-yo...
- jws 13y ago"64 bit" is the media way of saying ARMv8-A. The architecture has more registers and is generally designed and tuned for the current scale of processors being built. ARMv8-A instead of ARMv7 is the big deal. http://en.wikipedia.org/wiki/ARM_architecture#ARMv8-A http://en.wikipedia.org/wiki/ARM_architecture#ARMv8-A
- gfodor 13y agoWhat do you mean by "a phone?" Is the assumption here is that since it's a "phone" it somehow is not necessary to have top-tier computing power? The word "phone" is a holdover legacy from when these devices were used to just talk to other people in real time over voice. My current iPhone 5S is more powerful than a MBP from 2008.
- IvyMike 13y ago
- gnator 13y agoI think Apple pulled a good one on Android and other mobile OSes. With Android's ecosystem being so fragmented and Windows is still trying to get a foot hold on the apps market, a push to 64bit will further fragment their ecosystem.
- w1ntermute 13y ago> With Android's ecosystem being so fragmented Except that's just FUD: http://www.phonearena.com/news/New-Android-and-iOS-fragmentation-charts-are-just-as-flawed-as-the-term_id50332 http://www.phonearena.com/news/New-Android-and-iOS-fragmenta...
- acdha 13y agohttp://developer.android.com/about/dashboards/index.html http://developer.android.com/about/dashboards/index.html shows it's not, although it's definitely improving. The best way for that to continue is not to pretend the problem doesn't exist but rather to keep reminding carriers and vendors that this is one of the reasons they're less successful than they hope.
- rprospero 13y agoI'm not sure that I understand how the switch to 64-bit will further the fragmentation of Android. I would have thought that the Dalvik JIT would be ported to a 64-bit processor and the issue would be done. Short of running an application which requires more than 4GB of memory, why would a developer care if her code was running on a 32-bit or 64-bit processor? I don't follow the mobile space, so I'm probably missing something.
- jjdro 13y agoApple needs to capitalize on this by abandoning their current lameass numbering scheme and releasing the iPhone64 next year.
- danielsju6 13y agoA lot of people miss how big of an advantage Apple is continually taking by being first to market. People try to pin their mobile success on Apple fanboys or their "magic" user experience/ecosystem but Apple is simply just x-many months ahead of everyone's product roadmap and continually throwing curveballs at the rest of the players in the market. "Real world" benchmarks aside their 64-bit CPU has everyone else distracted, rethinking their product roadmaps, and demanding it in their devices while Apple works on it's next trick.
- w1ntermute 13y agoThere is no "magic" that having more computing power on a phone can enable. The vast majority of consumers are more than happy with the speed of their phone. The most impactful ways that Apple could significantly improve the iPhone right now would be to (a) double or triple the battery life, (b) make the screen unbreakable, and (c) make the screen bigger. These are the most common complaints I hear from iPhone users. Everything else really isn't that important. And I don't see any progress in any of those areas.
- codemonkeymike 13y agoThe screen size part is what keeps me on an android. With fat fingers its more important to me to be able to type out long messages without having to hit the backspace every few characters, that saves me more time then any speed increase that can be brought in the near term from 64bit processors.
- TrainedMonkey 13y agoa - I agree, I would pay for thicker/heavier iphone with 2x battery life. However this will fracture Apple's product lineup, thus economically unfeasible. b - screen on iphone 5S is already very strong. c - After lots of thinking I agree with Apple. Current form factor is just right for communication device [1]. If you need bigger screen, chances are you do not want a phone - you want a tablet. [1] Iphone user here, take this with a grain of salt. Over 3 models of iphone I never had a case. Phone is small enough for a proper grip with one hand while using thumb to control it. Anecdotal experience: I know 12 people with phones that have large screens. 7 of them had screens cracked due to dropping the phone. Every single one has a case (People who dropped their phones got a case after). What is the point of getting super light and thin phone just to put bulky case on it?
- socialist_coder 13y agoIf only Apple would give us bigger screens! I love iOS but the bigger screens of the top Android phones really have me wanting.
- jlarocco 13y agoPlease no. Some of the Android phones are so large they just look ridiculous. If a person wants a tablet, they should buy a tablet.
- socialist_coder 13y agoA tiny bit of additional horizontal space would be a big improvement IMO. I'm not talking Galaxy Note size, just S4 / HTC One size.
- epsylon 13y agoThere's a huge difference between a tablet and a screen size larger than the iPhone's.
- wyager 13y agoI like my phone to fit nicely in my pocket. If I wanted a 5-6 inch screen I would just go for a tablet.
- socialist_coder 13y agoI'm talking S4 / HTC One sized screens. http://internetzona.pl/wp-content/uploads/2013/03/spfsg.jpg http://internetzona.pl/wp-content/uploads/2013/03/spfsg.jpg The S4 still fits in your pocket. It's 2.75 inches wide. iPhone 5 is 2.31 inches wide. Anyways, I realize some ppl like the current form factor, I just wish Apple would give people the choice. I know in my circle of friends they're losing a lot of business to Android just because of the screen size.
- lucian1900 13y agoAs a Nexus 4 user, I envy the iPhone's dimensions. Even mine is just too big. Sadly, all small Android phones are shit.
- Nursie 13y agoIt it hit them in the gut it's because they wanted to supply the chips, and had a good thing going. 64 bit? Meh.
- adamnemecek 13y ago> A 64-bit processor handles data in bigger chunks than 32-bit processors, so it can get jobs done faster. If it is faster, it's not because it 'handles data in bigger chunks'.
- coldtea 13y agoWell, partly it is because of that.
- adamnemecek 13y agoExplain please. Are you talking about the fact that if you are doing calculations on 64-bit operands that it might take you fewer cycles?
- colanderman 13y agoYes; this is true of any vector operations in algorithms that are not constrained by memory bandwidth.
- noobiemcfoob 13y agoanyone who argues that 64-bit at the mobile level is worth anything other than being a marketing gimmick is an idiot. We've had 64-bit at the desktop level for years and the large majority of desktop programs have yet to find a way to take true advantage of it. All 64-bit does at the mobile level is introduce a ton of power loss for no real performance gain. The power usage Apple is reporting is likely due to other technological improvements that more than compensate for 64-bit's loss. The first poster had it right. All this does is screw up the rest of the industry, make them scramble, while Apple can buy time to figure out what to do next. Side note, Qualcomm's layoffs have little to do with their processor line...
- sifarat 13y agoAh! remind of the times, he fucked up himself. Now the baby (fakestevejobs) is on the right track. chuckles to himself selfishly
- ffk 13y ago"But now Apple can also claim an advantage in raw horsepower. The new 64-bit A7 chip is the smartphone equivalent of a big V12 engine." Except these performance gains most likely would of been seen on a 32 bit version of the chip. It's interesting to see how much marketing is put around 32 vs 64 bit chips and the effect it has on how people market. The biggest benefit is the ability to access more than 4GB of memory. For reference, the iPhone 5S has 1GB of memory. Eliminating the need for PAE and other expensive workarounds is definitely a bug plus. i64 and cheap doubles are certainly a bonus too. I suspect the primary reason for moving to 64 bit is not for performance gains now, but for future compatibility. Eventually, the iPhone 5S will be the oldest supported iPhone and running a 64 bit processor will reduce maintenance costs of needing to maintain a 32 and 64 bit line of software. I think this would be a much more informative article if the author had interviewed a few experts to discuss the benefits of 64 bits over 32 bits rather than just say they go faster which at this point is debatable.
- jjtheblunt 13y agoOr is the biggest benefit in this scenario the expanded availability, in 32bit mode, of registers, so that programs compiled for such a processor execute on-core significantly more than those not compiled for such a machine?
- lucian1900 13y agoRegisters are referenced explicitly, already compiled software could not possibly use more registers than it already does.
- alayne 13y agohttp://en.wikipedia.org/wiki/Register_renaming http://en.wikipedia.org/wiki/Register_renaming
- rayiner 13y ago> It's interesting to see how much marketing is put around 32 vs 64 bit chips and the effect it has on how people market. It's because it's a much more approachable pitch than "we doubled the size of the reorder buffers and added another instruction dispatch port." In Apple's case, they're simply using "64-bit" as a proxy label for all the other architectural improvements in Cyclone.
- leejoramo 13y agoHow close is Google to supporting 64-bit in Android? For Apple the story is much more than the 64-bit A7 chip, but iOS 7 and Xcode all being released with highly polished support for the A7.
- 7952 13y agoCompanies like Apple and Google have significant power to direct the investment efforts of their competitors. Adopting something just to catch up with Apple is a marketing gimmick. Using that money to add more RAM or improve the integration of the software is not a gimmick and could give an edge. Just like how Microsoft got distracted by Bing whilst Google built an OS.
- squozzer 13y agoMy fear is that touting a certain number of bits in the instruction set as a proxy for technological leadership will bite Apple in the ass. It's never been something they emphasized with much success -- e.g. the early PowerPC chips were arguably superior to their x86 contemporaries but it wasn't enough to compel users to switch. And whether Apple wants to buy into the chip game, well, good luck with that.
- salient 13y agoPrediction: Qualcomm wasn't actually ready to release an ARMv8 chip even at the end of 2014. They may try to do it now, but I don't think they were planning for it. From recent news it seems they were more interested in jumping on the "8-core" bandwagon (you'd think they learned their lesson when they rushed out their first quad core chip, the S4 Pro, in order to catch-up to everyone else and also have a "quad core chip", but no, they didn't). So how do I figure this? Because their first 64-bit chip they've just announced a few days ago (Snapdragon 410) is an ARM one! That blew my mind. Why? Because Qualcomm licenses ARM's architecture in order to build its own cores, and that should mean that they are coming out with a next-gen core faster than ARM's "stock cores". And yet their very first 64-bit chip is based on ARM's stock cores? That made it pretty obvious that Qualcomm was not prepared at all to make an ARMv8 chip, and I think it was mainly laziness, because of the nice position they enjoy in the Android market right now. They thought they could squeeze 3 years out of the 32-bit Krait, when normally it should've been two. Well the joke is on them. I certainly won't buy any phone in 2014 that isn't 64-bit, since I usually change my phones every 2-3 years, and I don't want to buy one of the very last 32-bit phones. I was actually expecting Qualcomm to release its own custom-made ARMv8 core early 2014 - and on 20nm! So I can't believe Qualcomm was actually going to rest on its laurels to such degree that they weren't even planning to switch to 64-bit, and probably 20nm either, even in 2014! That's insane, and only a company that thinks it has too much monopoly power in a market would do that. As Andy Grove used to say - stay paranoid about your competition. A paranoid company would've expected at least to some degree Apple to release its first 64-bit chip this year. But they didn't even have to do that. They just had to follow the original plan. The one that says release a new core every 24 months, and on a new process node (the one ARM is also following). What ever happened to that plan?
- DigitalSea 13y agoWhile 64 bit mobile processors are certainly a significant step forward for mobile computing, at present 64 bit processors for mobile are a gimmick because it's going to be a long time before the capabilities of such a chip can be taken advantage of. All this means is that we'll be seeing phones hit the market that have 16gb plus of RAM and well, I think we are a long way off seeing phones with that much memory hit the market. We are only seeing phones with 3gb of RAM that require equally as large batteries to power them like the Samsung phones. It took years for the PC market to transition from 32 to 64, and it'll take years for mobile to do the same. The amount of time it will take means competitors shouldn't worry because by the time 64 bit processors make sense, everyone will be manufacturing one. Sure memory addressing is just part of the picture and a 64 bit processor means data bandwidth is double that of a 32 bit chip which can be seen below 4gb of RAM, I think at present the iPhone isn't taking advantage of such improvements.
- wklauss 13y agoThere are other benefits in the transition, like a new and more efficient set of instructions, and iOS 7 is taking advantage of that.
- jjtheblunt 13y agoThe processor, in 32bit mode, offers more on-core registers, and a beefier instruction set. Programs compiled by a compiler aware of those distictions should significantly, measurably, perceptibly outperform those compiled for the older more constrained architectures.
- goggles99 13y agoAndroid has basically been a three legged horse in the speed/performance because of the Dalvic runtime anyway. Who cares about 32/64 bits. When Android comes out with it's new java compilation model and runtime (ART) in version 5 and claims that your phone OS and apps can now execute twice as fast, where does that leave Apple in the performance race? All of this does not really matter anyway. iPhone has always had better performance than almost every android phone. This has not saved them from losing massive market share. The PC/Mac history is repeating with Android/IOS.
- MaysonL 13y agoThe PC/Mac history is repeating with Android/IOS. Exactly: Apple dominates the high end, and is at 0% of the low (some might say junk) end.
- goggles99 13y ago>* Apple dominates the high end, and is at 0% of the low (some might say junk) end.* Where did you get the idea that Apple dominates at the high end? They haven't for a while now. The Galaxy S4 was outselling the iPhone 5 all by itself for several months (before the 5s came out). The collective of high end Androids have taken over the high end market on a seemingly permanent basis. Apple is at less than 50% and is on a steady decline vs the (high end) Android collective of phones.
- nilsbunger 13y agoAnandtech had a good overview page of what 64-bit (and more generally, Armv8) does for performance: http://anandtech.com/show/7335/the-iphone-5s-review/4 http://anandtech.com/show/7335/the-iphone-5s-review/4 Basically, the new arch increased registers, increased register widths, and cleaned up some architectural warts in Arm that hurt performance. The "4GB memory" issue is a red herring -- 64-bit is about making all the paths through the chip wider to process more per cycle.
- drill_sarge 13y agoIt reminds me of AMD Athlon64 period. Everyone claimed 64bit to be responsible for everything. In fact the majority of the performance came from the improvements over the k7 architecture (like integrated memory controller, hyper transport, better prediction, improved pipelines, cache etc.), new instruction sets and so on.
- gonzo 13y agoI can't really say it better than Mike Ash, so: <quote> Conclusion The "64-bit" A7 is not just a marketing gimmic, but neither is it an amazing breakthrough that enables a new class of applications. The truth, as happens often, lies in between. The simple fact of moving to 64-bit does little. It makes for slightly faster computations in some cases, somewhat higher memory usage for most programs, and makes certain programming techniques more viable. Overall, it's not hugely significant. The ARM architecture changed a bunch of other things in its transition to 64-bit. An increased number of registers and a revised, streamlined instruction set make for a nice performance gain over 32-bit ARM. Apple took advantage of the transition to make some changes of their own. The biggest change is an inline retain count, which eliminates the need to perform a costly hash table lookup for retain and release operations in the common case. Since those operations are so common in most Objective-C code, this is a big win. Per-object resource cleanup flags make object deallocation quite a bit faster in certain cases. All in all, the cost of creating and destroying an object is roughly cut in half. Tagged pointers also make for a nice performance win as well as reduced memory use. </quote> https://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and-you.html https://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-an... Android's Java runtime is going to need a lot of work to make it pull off a runtime feat like tagged pointers.
- lucian1900 13y agoSome JVMs already use tagged pointers for various things, often called "compressed pointers". It is of unclear utility for a language like Java and it could be easily added to ART if deemed useful.