That would be true for some apps but others would require code changes. And some older apps may never get that update. Even the ones that do, it could be months if not years. No question it's not a simple jump to make especially considering the potential benefit so far.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPad Air 2 Benchmark Points to A8X Chip With Triple-Core 1.5 GHz CPU, 2 GB RAM
- Thread starter MacRumors
- Start date
- Sort by reaction score
That would be true for some apps but others would require code changes. And some older apps may never get that update. Even the ones that do, it could be months if not years. No question it's not a simple jump to make especially considering the potential benefit so far.
And you guys call me crazy when I said the Macbook Air is destined to use the Apple ARM.
Ha !!
Yes!
Actually I was one of the "crazy" ones who thought it wasn't unreasonable.
But I didn't think it was coming this fast. The A8X seems like it's pretty much a legit low-end MBA SOC right now.
One would also have to compare CPU speed, there was no mention of what scale process was used in the A8X, and it is rumored that TSMC is making the A8X. All of which may factor into the incremental increase in performance.
https://www.macrumors.com/2014/10/15/tsmc-a8x-chip-12-9-ipad/
That would be awesome...and then Apple could start selling/renting 4K movies on iTunes, Netflix 4k...one can dream.
The writing is on the wall
Let's check the Geekbench 3 scores for the iPad Air 2
And now let's compare them to the Geekbench 3 scores for the stock high-end model of the 2014 Mac mini
What these scores mean:
With these kinds of numbers, it's only going to take a year or two before Apple starts using their Ax CPUs in Macs.
Let's check the Geekbench 3 scores for the iPad Air 2
And now let's compare them to the Geekbench 3 scores for the stock high-end model of the 2014 Mac mini
What these scores mean:
- a single A8X core clocked at 1.5GHz scores a 1492.
- a single i5 hyperthread clocked at 2.8GHz scores a 1537.
With these kinds of numbers, it's only going to take a year or two before Apple starts using their Ax CPUs in Macs.
If it will be 10x faster, then what? iOS devices can't replace OS X devices. It's not about performance, it's about software possibilities. Just compare iOS and OS X sizes. You just can't take app from desktop OS and use it with your fingers. Relax, your Macs were, are and will be more powerful even with more poor benchmark results.
Last edited:
At least in the Mac Mini and Air. Do I sense a convertible tablet in our future?
Intel, you have been put on notice!
Umm, you're not helping yourself and you did not dispute his point. You basically confirmed it is all about software that determines the difference between ARM and Intel x86 CPUs, not the hardware.
I can assure you without a doubt that Apple can build ARM CPUs to go into their Macs. OS X can be recompiled and the core of OS X has already been recompiled for ARM, alas iOS. Apple can recompile the rest of the stack to run on ARM.
The only problem with using ARM chips in Macs is that it prevents users from being able to use Windows since there is no consumer ARM version of Windows you can buy as far as I can tell.
Keep in mind that the A* series of CPU is designed to be as efficent as possible and in a power-constraint design. The Macs does not require this, give Apple 10 more watt, and that CPU can explode in performance.
I have ordered mine and being delivered tomorrow. Can't wait!
What real usage examples do you know of where more ram and extra processor will improve performance?
I'm not knocking it, just wondered what people thought. I use iMovie a lot so hoping video export time should be reduced dramatically.
What real usage examples do you know of where more ram and extra processor will improve performance?
I'm not knocking it, just wondered what people thought. I use iMovie a lot so hoping video export time should be reduced dramatically.
Love to see a list of apps that push this platform.
----------
Hell no! The Microsoft Surface split screen is buggy as all hell and prone to crashes. I bet somewhere deep in the Loop, this is running with not much success.
----------
Hell no! The Microsoft Surface split screen is buggy as all hell and prone to crashes. I bet somewhere deep in the Loop, this is running with not much success.
I use filmic pro and pinnacle studio can wait to seethe difference between the air and air2
Last edited:
It's a combination quad core/dual core chipset. Likely not all cores run simultaneously ever so it gives a somewhat wonky single/multi core comparison.
That's just my guess though. I initially thought the same thing, but the K-1 is not the average chipset.
Recompiling for a new CPU is rarely a big deal, like it used to be.
Actually recompiling by itself was never a big deal, but historically there was a lot of unavoidable additional baggage.
Apple, in particular, has virtually eliminated this baggage, making supporting a new CPU a minor update (in most cases -- and usually these days, if supporting a new architecture isn't easy, you've probably done some really screwed up things as a developer).
The K-1 actually scored higher in the single core performance- around 1900 in the 32 bit test (the 64 bit performance will be higher). But it's dual core so the 32 bit multi-core performance was measured at around 3200.
One thing to consider and probably the reason behind K-1 higher score is the faster clock rate (2.5GHz vs 1.5 for the A8X). The downside to this plus the fact the K-1 is using the less efficient 28nm die size, is that it will throttle much earlier. The A8X is probably built around a more stable performance hence the much lower clock speed (plus the 20nm die shrink).
Seems to not apply to iPad minis though.....my first gen mini is showing as $150 credit.....though it is technically newer than the iPad 2.
Consumers don't need Windows, they need software from it. Most software can be recompiled, but think about games. Nobody will recompile them. What to do? ARM<->x86<->Wine<->WinAPI?
What makes you think that would stop them? When did logic enter into the RAM discussion?
