Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is the kind of response that makes you appreciate how little knowledge so many members here actually have of what is happening. And there will be more of these comments to come in this thread, many more.

While there are many members on these forums who know about technology in general, are long time Apple users and generally work in IT industry, there is also same amount of absolutely clueless users who don't grasp basics of computer technology and those are the ones coming up with ridiculous statements or out of place ideas on how Apple hardware or software should be performing and working.
 
This is a seriously good results on 2 year hardware and using Rosetta! This benchmark is not run natively, so it's GOOD! I fail to see why people are so negative.
Secondly pretty Apple doesn't want the competition to know what they are capable as they for sure will be scared what the true performance will be and if they even have a chance to beat it.
Well, this chip was released this year and not two years ago. And this benchmark does run native ARM code (translated from x86 but still native). There are many caveats here for sure but let's be accurate.
 
Unless I'm being dumb (entirely likely), but when I searched Geekbench, I saw this. Using Geekbench 4.4.1 instead of 5.2.0. Much better scores. (I admit, I skimmed the 7 pages, but didn't see it posted yet).

View attachment 929078

the baseline CPU for geekbench 4 is different than geekbench 5. so you can't compare the two without some scaling.
[automerge]1593447956[/automerge]
also this thread is a perfect example of why apple didn't want benchmarks being run on these systems. the average user is nowhere near sophisticated enough to understand the meaning of a particular benchmark.
 
Yea because no one was going to do that :rolleyes:
People only got these machines loaned to them after signing a contract where they specifically agreed that they wouldn’t do this. You excuse breaking that with an eye roll and an “of course”? Huh. Remind me never to enter into any contracts with you.
 
Panicking over these results is like trying to run a PS4 game on a PS2 emulating PS1 and freaking out because it might not run Spider-Man properly.

No matter how much Apple, journalists and articles explain it everyone will fully misunderstand these results.
 
  • Like
Reactions: joeblough
So, I bet THIS is the real reason behind Apple giving up on all 32-bit apps with Catalina.

Most of my professional friends will not upgrade to Catalina until there are NECESSARY apps that require it.

It was a bad move to abandon 32-bit apps instead of encouraging developers to upgrade their apps. (A constant annoying popup when launched would do it... customers would complain about the popup until it's upgraded.)
 
  • Disagree
Reactions: tarasis
You are so right; if Apple does decide to launch a 2-year old design CPU, run it on just 4 of the 8 cores and under-clock it slightly and run everything through Rosetta then this benchmark will support your musings.

Many hold a view that Apple will not do any of the above. But you never know, you could be right.

To be fair, Apple launching Macs with 2-year old underclocked hardware is very typical of Apple.
 
  • Like
Reactions: Ulfric
Well, this chip was released this year and not two years ago. And this benchmark does run native ARM code (translated from x86 but still native). There are many caveats here for sure but let's be accurate.

Not really. Its a 2 year old chip with the last graphics core enabled after they got their improved yields. Its still an A12 cpu. That is 2 years old. A13s are a year old. If the Mac's use an A-branded chip, they will be A14. Or they could get a new designation as they get more desktop features.
 
  • Like
Reactions: Mescagnus
"It's not a basis on which to judge future Macs, of course, but it gives you a sense of what our silicon team can do when they're not even trying," he continued. "And they're going to be trying.

- Craig Federighi speaking about the DTK hardware.
 
People only got these machines loaned to them after signing a contract where they specifically agreed that they wouldn’t do this. You excuse breaking that with an eye roll and an “of course”? Huh. Remind me never to enter into any contracts with you.

You must not get into a lot of contracts if you think that everyone is trustworthy. At least, for your sake I hope you don't.
 
I wouldn’t disagree with Apple if they tracked what kits ran benchmarks and then disabled them. Rules are rules.
 
the baseline CPU for geekbench 4 is different than geekbench 5. so you can't compare the two without some scaling.

Oh duh, sorry, of course, had a brainfart about the baseline. Looks like it was the same device though. I know that this device is not going to be anything like the Apple Silicon that will be in the new Macs though.
 
  • Like
Reactions: joeblough
Maybe I am misunderstanding Rosetta 2, but why would there be much in terms of runtime performance penalty? I thought it was doing at-install translation of the x86 -> ARM calls so it then runs native from that point on. It is not doing on-the-fly emulation -- once the app runs it is going direct to ARM.

The translator must make conservative conversion in order to ensure that the produced ARM code is correct. Translating machine code optimally is in many ways more difficult than translating the source program written say, in C or Swift. Not only is the machine code targeted to a different architecture, so some patters just won't be optimal for the ARM host, but
the high-level language code contains more information that signals the developer's intent. There are other issues, like certain indirect operations, which often can't be translated directly and most likely have to be trapped and handles specially.

Not to mention that Rosetta has to be fast, so it can't spend too much time optimizing.

But again, these first results are encouraging. Not only is the performance quite good, but, more importantly, it can run a complex x86 software suite like Geekbench correctly! Which is quite a feat.
 
"It's not a basis on which to judge future Macs, of course, but it gives you a sense of what our silicon team can do when they're not even trying," he continued. "And they're going to be trying.

- Craig Federighi speaking about the DTK hardware.

"Apple hasn't been trying for years, but we pinky swear we will soon!"
- Craig Federighi

I guess that explains some things.
 
  • Disagree
Reactions: jdb8167
Why would someone run geekbench and not something like a Pi test or something else they could run through he command line and would know is native. It would surprising that these devs with dev kits have such a nominal understanding of actual computer science if I didn't see it daily.
 
Even considering all those caveats (for the sake of argument lets add 30% to those scores) It still seems weak. Way below of Renoir 15 watt chips. And don't forget Renoir is Zen 2, Van Gough will be Zen 3 with 20% performance jump in IPC, plus extra 200-300Hz frequency because of 7NM+ mature node.
 
  • Like
  • Disagree
Reactions: jdb8167 and mrxak
"It's not a basis on which to judge future Macs, of course, but it gives you a sense of what our silicon team can do when they're not even trying," he continued. "And they're going to be trying.

- Craig Federighi speaking about the DTK hardware.
That's obviously just a PR talk. Unless he is really trying to say that they were not trying to design the best chip for iPads.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.