How M1 Macs feel faster than Intel models: it’s about QoS

Post by _r0fz » Tue, May 18, 2021, 11:29 PM UTC

astrange wrote: post #340

8fGTBjZxBcHq wrote: post #215

Earlier quoted context omitted.

This is a lot of really well expressed information that completely fails to grapple with the fact that most developers write code for the web and apple computers are extremely popular among web developers. All of the things you mentioned are also true of intel macs, which again are wildly popular among web devs of all kinds. If you can't explain the popularity of those machines in spite of those limitations, I don't…

> This is a lot of really well expressed information Well, no, it's all totally made up.

Post by MonaroVXR » Wed, May 19, 2021, 9:59 PM UTC

emteycz wrote: post #370

davrosthedalek wrote: post #357

Earlier quoted context omitted.

Sure, but my macbook pro has cooked it's display /twice/ now. Didn't go to sleep properly, and it overheated in my laptop bag. No good way to check for it, because no LEDs on the outside. Only way to check is to see if the fans switched on after five minutes in the bag.

You don't want to know what the Dells are capable of doing. My XPS 15 2020 literally got on fire somewhere on the motherboard - not even a battery thing. Then I decided to go Apple only.

Post by [deleted] » Fri, May 21, 2021, 4:32 PM UTC

coder543 wrote: post #384

jfrunyon wrote: post #383

Earlier quoted context omitted.

And yet it is extremely unlikely that it's linear or anywhere near it.

What is "linear" in this context? If the Y-axis is performance, what is the X-axis? That statement doesn't seem to make much sense without any additional explanation. If I run a benchmark for a program on the M1, that's a single data point. It's hard to call a single data point "linear", "quadratic", or anything else... and you can't really put multiple benchmarks on the X-axis, because they're measuring different th…

Post by jfrunyon » Fri, May 21, 2021, 4:38 PM UTC

coder543 wrote: post #410

cptskippy wrote: post #409

Earlier quoted context omitted.

> I have no reason to believe that the M1's performance starts tanking if you run it for longer than a few seconds This statement speaks volumes about your bias. You're immediately on the defensive and assuming we're attacking the M1 rather than the assumptions made in a test and it's methodology. No one was implying that the M1's performance would tank. I specifically conjectured that perhaps x86, not M1, might have…

> But if there's just a 10 second warmup penalty on x86 the compile time might only be 60 minutes + 10 seconds. But that doesn't make any sense, as I previously asserted. That's just not how any of this works. x86 is not suffering a "penalty". It doesn't need time to "warmup". I already discussed my views (based on actual real world experience) on all of this, but you conveniently bypassed those statements. > This st…