
"In essence, the power they contain means you can use a MacBook Pro to build 3D models almost as easily as you use a Neo to make a spreadsheet. Geekbench proves my point. Look at these Geekbench scores and you'll see what I mean: M1 Mac: 2,386 single-core; 8,571 multi-core. MacBook Neo: 3,467 single-core; 8,668 multi-core. M5 Mac: 4,227 single-core; 17,802 multi-core. M5 Pro Mac: 4,280 single-core; 28,030 multi-core. M5 Max Mac: 4,268 single-core; 29,159 multi-core."
"The data shows, that for the toughest multi-core tasks, Apple has more than tripled computational performance in just five years. It is also relevant to note Apple's statement that the M5 Pro/Mac systems deliver over six times the peak AI compute we got from the original M1 systems."
"That's faster progress than Moore's Law, which says computational performance should double every 18-24 months, and that trajectory shows how quickly Apple's Macs have become highly competitive at the highest reaches of the PC industry. Gone are the thermal throttling limitations that plagued Intel Macs during high-end tasks, in comes the capacity to use Apple's computers when sustained performance is required."
Apple now offers computing solutions across all performance tiers, from the affordable MacBook Neo for general purposes to the high-end M5 MacBook Pro for demanding tasks. Geekbench benchmarks demonstrate significant performance gains: M5 Pro and Max systems achieve multi-core scores of 28,030 and 29,159 respectively, compared to the M1's 8,571. This represents more than triple the computational performance in five years, surpassing Moore's Law's predicted doubling every 18-24 months. The M5 Pro and Max deliver six times the peak AI compute of original M1 systems. Apple Silicon architecture eliminated thermal throttling limitations that plagued Intel-based Macs, enabling sustained performance for compute-intensive applications like 3D modeling.
#apple-silicon-performance #macbook-pro-m5 #benchmark-comparison #high-performance-computing #ai-compute-capabilities
Read at Computerworld
Unable to calculate read time
Collection
[
|
...
]