Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is a very interesting development. Assuming that Geekbench scores are normalized across platforms (arm/x86), the single-thread score is better than my 9900K @ 5GHz.

It is. Skylake-derived Intel CPUs are fairly mediocre at this point.

You'd have to look at Tiger Lake to see some competitive numbers again.
 
  • Like
Reactions: PickUrPoison
For perspective,

Top spec'd MacBook Pro 13" with Intel I7: 1348 single, 4908 multi
Top spec'd MacBook Pro 16" with Intel I9: 1105 single, 7114 multi

These are for the very top spec'd models of each, and the highest scores I can find of many posted. The "A14X" derivative that will likely go into the new MacBooks will likely exceed the multi on the current 13" Pro and be very competitive with the 16"

Holy heck, these new chips when put in an MBP are going to scream....

I still wouldn’t buy first gen, but it would certainly be tempting.
 
It is. Skylake-derived Intel CPUs are fairly mediocre at this point.

You'd have to look at Tiger Lake to see some competitive numbers again.
What exactly does "normalized" mean in this case? Not using the features available exclusively in Intel CPUs? AVX 512 would be one example.
 
  • Like
Reactions: Woochoo
As CPUs get faster, operating systems get slower, so really the purpose of these faster chips is to just keep up
This is cute to say, but not true.
It may not be true for OS's, but it is often true for applications.

The contemporaneous versions of Word and Excel on my then-new mid-range 2008 based MBP were snappier than the contemporaneous versions of Word and Excel on my then-new top-of-the-line BTO 2104 MBP. Plus spinning beachballs are much more common with the latter than the former.

So in some ways the chips (at least for applications requiring single-core performance) are not keeping up with the added overhead that accompanies the newer apps.

Here's a comparison I did using the same machine (the 2014 SSD MBP listed in my profile below) with three different versions of Word, along with TextEdit and Pages. This is not disk I/O limited. After the clipboard contents are copied into Word (and I assume Pages as well), the programs have to "process" it for formatting. So nearly all of this is due to application overhead.

Note the stunning difference in overhead between Word 2008 and Word 2011/2016. My 2014 MBP would need to have a single-core speed 10x faster than that of my 2008 MBP, to have Word 2011/2016 on the former be as snappy as Word 2008 on the latter. And since single-core processing speeds didn't increase 10-fold between 2008 and 2014, we're actually going backwards here in real-world user waiting times.

Time to copy contents of 3 MB text file (114K lines) from the clipboard into:
TextEdit (Yosemite): < 1 sec
Pages (Yosemite): 10 sec
Word 2008: 14 sec
Word 2011: 142 sec
Word 2016 (Preview): 121 sec

And don't get me started on Excel. I often need to switch quickly between tabs, and the delay in doing so (as well as the delay in renaming tabs) drives me crazy.

Part of this is that Office was at the time (and I find still is) poorly optimized for the Mac. Here I performed the same test, at the same time, on the same machine, in Bootcamp under Windows 7:

NotePad (text editor, similar to TextEdit): < 1 sec
Word 2016 (Preview): 18 sec (8 x faster than under OS X)

Contributing to the problem is that most of the increased processing power offered by newer chips over the past decade has come from more cores, rather than increased single-core speed. There are reasons for this but, regardless, this means most of the advancement in chip performance doesn't benefit Office programs, which (with the exception of certain functions in Excel) are purely single-threaded (yes, an open Word application will have many threads, but only one of these can be running at a time).
 
Last edited:
Are we comparing processors installed in a tablet and a phone? I am not sure it makes much sense. Often the same processor may be set up quite differently depending on available power and cooling.
 
I'm trying to decide between the new Air and the 11" Pro, and really my main consideration is how the OS responsiveness will be holding up 2-3 years from now. Both CPUs are very powerful, but I feel that the extra RAM in the Pro might be a big deal as iOS/iPadOS grows. Which is going to start showing it's age first, the CPU or the RAM?
I agree with the other poster — the Pro is clearly a better value, and it will still be relevant for many years to come.

For reference, I still have an iPad Air 2 from 2014 running an A8X that performs well with zero problems.
 
  • Like
Reactions: PickUrPoison
It is quite risky comparing a small powered cpu with small set of instructions to a 45~125 watt chip with a lot more instructions (remember atom series with micro ops that is only run at half the performance of their counterpart with CISC at the same clockspeed). I wouldn't be surprised if the next mac with Apple Silicon would run some softwares (including benchmarks) better than the Intel one, while the other run worse.

the whole RISC vs CISC thing is an anachronism. Nobody takes it seriously any more.

intel’s complex instructions are split in to simpler micro-ops internally, until the result looks very RISC-like. At the same time, ARM has introduced all kinds of extensions such as pointer authentication (not to mention other instructions introduced by licensees), which looks very CISC-like.

ultimately it’s all about chip designers, and where they feel the appropriate balance is for each chip they design.
 
Compared to best Qualcomm Snapdragon 865 phone:

A14 is a beast, that single core performance is insane. I don't see Apple giving up it's lead in chip performance anytime soon.
Until Microsoft also realizes that using reference designs won’t cut it. I wouldn’t be surprised to find out they’re working on their own 64 bit only ARM version of a system that will run Microsoft Office and Xbox Game Pass. ;) Priced right, it would sell tons.
it’s still not gonna be enough to justify a switch
There don’t need to be many switchers for Apple to maintain their current macOS marketshare... around half of all folks buying a Mac every year are new to Mac, most likely having never owned a computer before. Plus, remember, the big future goal for Apple is to move everyone over to iOS. And, when you consider that there’s more iPads sold than all laptops, they’re well on the way to that end.
 
Comparing benchmarks across architectures is a fools errand.

Less speculation and hoping, more waiting for reality.
except the whole point of the benchmark is to make it possible to compare benchmarks across architectures...

Not sure what's speculation and hoping when it comes to
- single core speed
- mulit core speed
- clock rate
- TDP

Each of these are hard facts & numbers, nothing about it is speculation.

About putting 9 A14s in one machine, admittedly, that's wishful thinking and won't happen -it's just not as simple as that. But Apple making an A15x with 12 or 24 cores is definitely future expansion possibility

I think they'll hit the 3Ghz wall also by the way, so they will need to scale on cores and multi core scores. Even if the 3Ghz wall has now been expanded to 5Ghz under certain right conditions and circumstances, for short boost times, etc. The fact is around 3Ghz it becomes increasingly more difficult to up clock rates as certain physical limits are encountered.
 
As CPUs get faster, operating systems get slower, so really the purpose of these faster chips is to just keep up
This is cute to say, but not true.

agreed, never before devs have had such a tech stack API that largely handles under hood: lazy evaluation, performant memory management, even multithreaded and asynchronous operation with minimal boiler plate code...

In fact, I think making a very badly performing application with today’s APIs and cpu power boils down to not knowing properly some key basics.
 
Bildschirmfoto 2020-10-04 um 00.14.29.png
This is just nuts! By the way, that processor dissipates 165W.
 
Last edited:
The iPad Air 4 is going to be a heck of a good tablet for a lot people. Makes me wonder how good (and irresistible!) the next gen iPad Pro will be.
That is what I am looking forward to see the next generation iPad Pro models. The iPad Air 4 is a good deal, but its not a iPad Pro replacement.
 
Last edited:
If only the education deal applied to the Ipad Air, sadly only the pro's really benefit from it. Still think the IPP is the better option, hopefully the air doesnt have bendgate issues.
Why do the newer iPads bend; is it the square, hollow aluminum chassis? My iPad 6 is a workhorse. It can handle a lot. Although it did incur the bright, white spot and the home button. I hope Apple solved this as well. Super annoying.
 
Apperantly the middle part of the ipad is the weakest, where the microphone is placed on the side. Not sure why but apple says bending is normal but wont cover it as a defect.
Bending is normal. Amazing. They say the same about the bright white spot, until trade-in time.
 
  • Disagree
Reactions: matrix07
Good point, well taken, however I was focusing on the majority of users, who never use blur filters - most PC users are corporate drones like myself, not creatives. We need Excel, Powerpoint, Word, Outlook, etc. to get our work done.

Regarding the A14, I'd be getting the upcoming Air if I hadn't bought an iPad Pro this spring. This looks like a big winner.
We (at least many of us) used to have to turn off automatic recalculation to be able to make spreadsheets usable, esp if you were using certain exponential(?) functions. I’m probably thinking of Lotus 1-2-3, but iirc F9 was recalc.

You’d add some rows, copy/fill, etc. then hit recalc. Maybe a second, maybe much longer. You’d literally see the changes ripple through on-screen as the cells recalculated 😡 Good times 🤣
 
  • Like
Reactions: NetMage and I7guy
Bending is normal. Amazing. They say the same about the bright white spot, until trade-in time.
“Bending is normal” is not something Apple has ever said. Nor have they said the same about any “bright white spot.”
[automerge]1601765524[/automerge]
We (at least many of us) used to have to turn off automatic recalculation to be able to make spreadsheets usable, esp if you were using certain exponential(?) functions. I’m probably thinking of Lotus 1-2-3, but iirc F9 was recalc.

You’d add some rows, copy/fill, etc. then hit recalc. Maybe a second, maybe much longer. You’d literally see the changes ripple through on-screen as the cells recalculated 😡 Good times 🤣

i forgot about that!

Used to also be an issue where you could create calculation loops, and freeze lotus. And yes, I believe it was f9.
 
  • Like
Reactions: PickUrPoison
Truer words have never been spoken. Developers are spoiled with ridiculous layers of abstraction that were fantasy just 20 years ago. A lot of them are lazy, too, not coding to the highest possible efficiencies. Why bother tightening up your code when the chips are so fast?

And before anyone starts crying up a hissy fit over my calling developers spoiled and lazy, when was the last time you actually, really, had to truly program anything? Writing scripts and HTML is not coding.
You need to look up "premature optimisation".
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.