Thinking about ordering the new Mac mini with M4 Pro. I’m wondering is it really worth bumping up from the 12 core to the 14 core CPU? Mostly this will be used for Xcode. Any thoughts?
Notice: there are 2 CPU core differences which are performance cores that consume more power.
the question is, are they optimized to be used only when it is needed or it is always active?
I would go with the 14-core model. Extra two performance core will be helpful for code compilation.
Yeah, that's the way I'm leaning at the moment. I think I'll wait for some performance benchmarks to make sure the cooling solution doesn't cause any throttling before I order though...
A throttled 14-core is still better than a non-throttled 12-core.
I personally went with the 14-core upgrade. I plan on using this as my main machine for at least 3 years and think the price difference is worth it in the long run. I also noticed that the M4 Max starts at 14-core CPU. The way I see it, for $200 more, we get base M4 Max CPU performance (albeit with less powerful GPU) without having to pay M4 Max money. The cheapest available M4 Max is the 14in MBP starting at $3,199. Hope this helps!
Thinking about ordering the new Mac mini with M4 Pro. I’m wondering is it really worth bumping up from the 12 core to the 14 core CPU? Mostly this will be used for Xcode. Any thoughts?
But even this setup does not stress my 10-core M2-Pro mini.
I assume you use xcode now. Look at Activity Meter and see if you ever max-out the CPU. I bet not unless you are compiling a very large project with many *.c files or if you have a bunch of simulated iPhone hardware running apps.
software development does not stress the processor. Mostly you are just typing
Many times when I am wringing software I'm in a Linux environment inside a virtual machine. Doing that can really eat up RAM and CPU because I need to give four cores and 16GB RAM to the virtual machine but I like to run the editor windows on the Mac while the files physically live on the Synology NAS. But even this setup does not stress my 10-core M2-Pro mini.
This. Everytime I make the decision to upgrade, I spend too much energy trying to figure out if I'm buying a beefed up machine to salve my resource anxiety when I would have been fine with a more entry level model. I run into people who can run circles around me as a developer and many of them are doing it on an 8GB MBA.
That I can afford it doesn't change that I feel really stupid when I waste money, but once I make my decision, I'm good at living with it. No regrets... I front load all of the pain 😂
I know exactly what you mean. That's really what this post is all about for me. On the one hand I could probably get by just fine with the base spec M4 with the 512GB SSD at just $799, but all those extra cores on the M4 Pro are whispering to me 😋
Yes, a faster CPU would compete builds in a shorter period of time. The software is written to consume a fixed maximum percentage of your processing power, so that one can continue to do other things. So a 50% faster CPU will roughly translate into 50% faster compile times even though neither CPU will be stressed to the max.Well, you're correct I currently don't max out the CPU (Macbook Pro M1 Pro). Even so, wouldn't a faster CPU still complete builds in a shorter amount of time? Or if I'm not maxing out my M1 Pro, should I really just be focused on the single core speed of the M4 as the primary opportunity for a boost in compile speed? I'm in the habit of recompiling very frequently so any improvement there will be a very welcome quality of life boost.
Curious, what memory and storage size you went with? And your workload?I personally went with the 14-core upgrade. I plan on using this as my main machine for at least 3 years and think the price difference is worth it in the long run. I also noticed that the M4 Max starts at 14-core CPU. The way I see it, for $200 more, we get base M4 Max CPU performance (albeit with less powerful GPU) without having to pay M4 Max money. The cheapest available M4 Max is the 14in MBP starting at $3,199. Hope this helps!
I agree with upgrading to 24GB RAM before anything else, but I disagree about upgrading from 24GB to 48GB RAM. Unless a person works with the Adobe or other memory intensive media creation software on a regular basis, RAM beyond 24GB isn’t needed (nor will it make much if any difference) in the next 3-5 years. Memory not needed by applications is just used by the OS for cache which makes a <1% difference in performance. By the time it the extra memory is needed for common applications, you’ll want a new computer anyway. In contrast, the upgraded processor will make a difference (even if modest) for every day use from day 1.If you have the money, it is better to spend it on increasing RAM. That is more likely to provide you a future benefit than a couple more cores
Single core speed affects pretty much everything and it’s the same for both CPU’s. The 14 core model will only be faster after the 8 performance cores on the lower spec one are saturated.Even so, wouldn't a faster CPU still complete builds in a shorter amount of time? Or if I'm not maxing out my M1 Pro, should I really just be focused on the single core speed of the M4 as the primary opportunity for a boost in compile speed?
Yea 6% betterA throttled 14-core is still better than a non-throttled 12-core.
Same here. In the end I didn't think I would get much value from the extra two cores. The 12 core model is plenty fast.Very happy with my 12 core
I see you haven't launched the iPhone Simulator lately. Takes a shockingly long time on my M1, with all cores on full blast.I assume you use xcode now. Look at Activity Meter and see if you ever max-out the CPU. I bet not unless you are compiling a very large project with many *.c files or if you have a bunch of simulated iPhone hardware running apps.
Never worked with Swift before, huh?software development does not stress the processor. Mostly you are just typing