What you need to know
- More benchmarks are starting to surface for Apple's new iPad Pro.
- They seem to show that gains on the 2018 A12X are fairly minimal.
- There was some increased graphic performance thanks to the new A12Z however.
More iPad Pro benchmarks suggest that Apple's iPad Pro is testing only slightly ahead of the 2018 model.
As reported by MacRumors:
The results seem to confirm earlier reports from My SmartPrice, who suggested that the new iPad Pro offered very slight benchmarking gains over the 2018 model.
Of course, Apple is far less concerned with benchmarking than it is with user experience. However, its A12Z Bionic Chip was highly touted by Apple at the launch of the new iPad Pro, its press release stating:
Whilst the A12Z may not be the leap in performance some were hoping for, the 2018 iPad Pro was no slouch. It's also important to remember that this is only a slight tweak to an existing processor, the A12, rather than a component overhaul or revamp.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple. Follow him on Twitter @stephenwarwick9
Apple obviously knows this isn't a major upgrade from the 2018 model. This is for people using the 2017 model and below, and it will be a significant upgrade for them.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.