iPad Pro The A11 Bionic destroys the A10X Proof.

[Macintoshrumors]

Better get shot of my 3 year old iMac then

.....weak

by 2017 standards at least.

 

[iRobertM]

The articles goes into greater detail. Here’s the short version the A10X only shows up as a 2 Core CPU as being available at any given time Either an app is using 2 High Power Cores or 2 Low Power Cores all 4 Cores can not run at once.
However the A11 Bionic has flexibility and is capable to have all 6 Cores running at the same time or independently as needed. Marking a monumental change.

http://www.idownloadblog.com/2017/09/11/iphone-x-a11-six-cores/

Yet another reason I’m glad I didn’t get a 10.5” IPad Pro.

FYI, using the word “destroys” in the title is an instant eye roll and turns your thread into a joke.

 

[iPadDad]

Guys this is not true!!! Or am I missing something?!?!?! Look at the Metal score, the A10X dominates the A11

http://browser.geekbench.com/ios-benchmarks/

 

[kazmac]

Technology is constantly evolving, and in some cases, improving. New tech: fast and perhaps better with a pinch of "Ooooh Shiny." thrown in.

Unless they release a Mini with Pencil support, I am good iPad-wise.

I enjoy what I own and leave it at that.

 

[UBS28]

The articles goes into greater detail. Here’s the short version the A10X only shows up as a 2 Core CPU as being available at any given time Either an app is using 2 High Power Cores or 2 Low Power Cores all 4 Cores can not run at once.
However the A11 Bionic has flexibility and is capable to have all 6 Cores running at the same time or independently as needed. Marking a monumental change.

http://www.idownloadblog.com/2017/09/11/iphone-x-a11-six-cores/

Yet another reason I’m glad I didn’t get a 10.5” IPad Pro.

1. CPU power is pretty much the same. If the A10X is struggling, then the A11 will also struggle with a CPU related task.
2. GPU on the iPad Pro is 2X more powerful than the A11. Why else you think the iPad Pro has pro motion and the iPhone X doesn’t.

So A10X > A11 in terms of power.

 

[Menel]

How long we gotta wait for A11 and FaceID?

 

[jdiamond]

Why? What are planning on using the iPad for that requires such a fast processor. The A10 is plenty fast and I see no downsides of using the iPad. I think its silly to hold off on a product that works so well, just for the hope and promise a future version will be even faster.

To expand on your point of existing software: Any iOS developer would be a fool to try to market an App that runs too slowly on the fastest iPad in existence. Trust me - however fast a processor is, the way the developer optimizes his software matters a whole lot more for performance. And that same developer would make a lot more money if his app ran well on the slowest iPads still in mass use.

As a developer, I always try to develop on somewhat outdated hardware so I don't fall into the trap of thinking my code is fast enough when it's not. You can always make code fast enough. And anything the CPU is too slow for you can leverage the GPU for. Perhaps a more difficult limitation is size of memory for Pro-code where you have to work with enormous models, e.g. CAD software or pro-rendering software. But even here, you have no choice but to support the iPads people have, so if you can't figure out how to do that, another developer will.

 

[spiderman0616]

I have been waffling back and forth on whether or not I'm going to upgrade my 10.5" Pro. It's really hard to decide for sure without seeing the new one first and hearing the feature list.

That being said, a faster processor would NOT be on the list of reasons I'd upgrade. The A10X in my 10.5" Pro has NEVER made me wish I had a more powerful processor. It is a screamer.

 

[CrazyForCashews]

That being said, a faster processor would NOT be on the list of reasons I'd upgrade. The A10X in my 10.5" Pro has NEVER made me wish I had a more powerful processor. It is a screamer.

Agree. One of the many things that the 2017 iPad Pro's got right were the processors. The tablets themselves are very responsive without showing any hint of lag. It would be hard to notice a speed improvement from a newer processor when the A10X already chews through anything you throw at it.

But I am curious to see what the 2018 iPad Pro's have to offer. Judging by rumours, it seems that the new iPad Pro's might be the most radical design for iPad's since their inception; as radical and different like the iPhone X was.

Hopefully the price won't be as radical as the X.

 

[rexboe]

When updating my iPad pro 10.5 and iPhone 8 plus the iPad finishes several minutes before the iPhone 8 plus. Especially during the preparing update phase.

 

[Homme]

The articles goes into greater detail. Here’s the short version the A10X only shows up as a 2 Core CPU as being available at any given time Either an app is using 2 High Power Cores or 2 Low Power Cores all 4 Cores can not run at once.
However the A11 Bionic has flexibility and is capable to have all 6 Cores running at the same time or independently as needed. Marking a monumental change.

http://www.idownloadblog.com/2017/09/11/iphone-x-a11-six-cores/

Yet another reason I’m glad I didn’t get a 10.5” IPad Pro.

And since Geekbench 6 just came out, let’s test multi core scores shall we

With Geekbench 5 A10X was on par multi core wise with A11

But with Geekbench 6, not only does the A10X smoke the A11 but thanks to real world usage ( thinking outside the box) A10X in multi core hovers around A12 territory, between the XR/XS ( assuming the makers of Geekbench included RAM as part of real life usage the A10X iPads beat out the XR since that has 3GB of RAM)

 

[Yebubbleman]

The articles goes into greater detail. Here’s the short version the A10X only shows up as a 2 Core CPU as being available at any given time Either an app is using 2 High Power Cores or 2 Low Power Cores all 4 Cores can not run at once.
However the A11 Bionic has flexibility and is capable to have all 6 Cores running at the same time or independently as needed. Marking a monumental change.

http://www.idownloadblog.com/2017/09/11/iphone-x-a11-six-cores/

Yet another reason I’m glad I didn’t get a 10.5” IPad Pro.

Except there was never an iPad with A11 Bionic and if we're having an Apple SoC history lesson here, A11 Bionic marked the end of 32-bit ARM support (which is largely what caused A6 to be dropped from iOS 11 [and for all 32-bit apps to stop functioning in iOS 11 even on supported Apple SoCs that had 32-bit ARM instruction sets], despite running iOS 10 better than any iPad/iPhone has ever run their final OS). Not saying A11 Bionic sucked. Just that there were trade-offs.

Also, there are many more reasons why you ought to be glad that you didn't get a 10.5-inch iPad Pro. That display frequently had many issues, for instance.

“I’m glad I didn’t get the iPad Pro 10.5 2nd gen because the A12 destroys the A11X”

No such iPad or SoC...? Like, I get that it's sarcasm, but it's not like there weren't real and significant differences between A10/A10X and the Bionic generation of A-series SoCs. And, sure, an iPad with the standard non-X/non-Z A12 seems old these days. But to dismiss it as standard evolution dismisses the fact that A10 to anything after it was substantial. Apple didn't know what they were doing during their first bout with asymmetric cores.

 

[Homme]

To write here, the fact that the A10X is still getting full support as of the A10X Apple TV is living proof that the A11 is **** as ever.

And if the 7th gen iPad getting iPadOS 18 with its A10 but A11 getting up to iOS 16 is more proof that the SoC sucks even more

 

[Homme]

“I’m glad I didn’t get the iPad Pro 10.5 2nd gen because the A12 destroys the A11X”

I know it’s old but I’m glad there was no A11X because Apple did not find this hardware flaw until the A11 dating back to the A5 SoC. And also its GPU overheats to a point that I think rendering something at 60fps isn’t possible or some point but the A12 fixed all of the A11’s flaws and more

 

[leifp]

Better get shot of my 3 year old iMac then

I really miss that iMac. Or the idea of it. I had that model (identical except I had the 3TB drive) from early 2015 until its retirement (to become a WinPC for a friend’s school age children) three years ago. This was the first time that I had a computer that worked perfectly for my uses and did so for nearly seven years. It started to lag noticeably when I replaced it with an M1 Mac mini. An experiment that failed but happily Apple released the Pro/Max chip variants and I’ve been semi-happily using my M1Max MBPro ever since. Because I could never have hoped that Apple would release the mythical “headless Mac”… I’ll pick up an M5 variant of the Studio next year. Unless Apple decides that an M5Pro/Max in a 32” 6K iMac body is a thing. Hope burns eternal!

Yup yup, so happy to find a computer that I loved to use from the moment I got it for almost seven years. First time ever. And now I’ve had the M1Max MBPro for nearly four years and the only “need” I have for its replacement is that I still hate laptops…

 

[Homme]

When updating my iPad pro 10.5 and iPhone 8 plus the iPad finishes several minutes before the iPhone 8 plus. Especially during the preparing update phase.

That’s because that iPad has identical multi core score to A11. 4GB of RAM Compared to 3GB on the iPhone 8 Plus. And despite A10X iPads not getting iPadOS 18 and imagine iPadOS 26 for it. That would still handle it well

But then if Apple TV HD can get supported for over 10 years ( with the Apple TV HD/4K being the only Apple TV Models and the only OS 26 Models to not support Liquid Glass which is understandable given the age of the processors since every other OS 26 ARM Device capable of Liquid Glass is an A12 or Later. I totally agree with the A8 2GB of RAM, The last remaining Intel Macs for macOS Tahoe gets Liquid Glass but a caveat… macOS 26 Tahoe doesn’t support FireWire at all. I totally disagree I think it should be left in for at least one more year until the final death of Intel Mac’s not getting macOS 27 then get rid of FireWire Support. Because this is one thing that some macOS users ( intel ones) want until Tahoe not Sequoia

But FireWire is sparsely used nowadays