Leaked Apple M5 9 core Geekbench scores

Re:Leaked Apple M5 9 core Geekbench scores by rafaelmn on Wednesday October 01, 2025 @05:20AM (#45435817)

Not really - I bought an M4 Air to check how my dev ecosystem (.NET) would run on the ARM/Apple silicon and while its usable its noticeably slowing me down in my day to day with Rider. I will be getting the M5 pro because the performance is a bottleneck for me (even incremental builds take a while). Also I regret not getting at least 30gb ram (Amazon only had 24gb configurations) because with docker running I constantly hit the memory pressure thresholds .

Which is not to say that the Air is a bad device, its an amazing laptop (especially for the price, I have not seen a single Windows laptop with this build quality even at 2x price) and the performance is good - that if I was doing something like VSCode and node/frontend only it would be more than enough.

But also people here oversell its capabilities, if you need anything more CPU/Memory intensive PRO is a must, and the "Apple needs less ram because of the fast IO/memory" argument is a myth.

[ Parent | on HN ]

Re:Leaked Apple M5 9 core Geekbench scores by saagarjha on Wednesday October 01, 2025 @05:30AM (#45435880)

Have you checked what is slowing it down?

[ Parent | on HN ]

Re:Leaked Apple M5 9 core Geekbench scores by tonyedgecombe on Wednesday October 01, 2025 @09:57AM (#45437807)

I wonder if it’s Docker as it runs in a VM on macOS.

[ Parent | on HN ]

Re:Leaked Apple M5 9 core Geekbench scores by rafaelmn on Wednesday October 01, 2025 @11:01AM (#45438505)

You can control how much RAM gets allocated to the Docker VM and I keep that at 2GB which is not that much. I am not running stuff inside docker locally just using it to boot up stuff like pg/rmq/redis

[ Parent | on HN ]

Re:Leaked Apple M5 9 core Geekbench scores by rafaelmn on Wednesday October 01, 2025 @10:59AM (#45438475)

Just everything syphoning down RAM, standard office/desktop stuff like Slack, Chrome, Mail, Calendar, Messages, a few IMs will easily eat up over 12 GB, then add in VSCode, Rider, Docker (which I cap at 2 GB ram) - I am swapping gigabytes when I have multiple tools running.

But even when I kill all processes and just run a build you can see lack of cores slow the build down enough that it is noticeable. Investing into a 48gb ram/pro version will definitely be worth it for the improved experience, I can get by in the meantime by working more on my desktop workstation.

[ Parent | on HN ]