Live data from Hacker News

Apple Readies MacBook Pro, MacBook Air Revamps

bloomberg.com

161–170 of 351 posts

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#161
The new Macbook Pro sounds amazing. The 64gb RAM possibility suggests a lot of things, some of which confirmed by the artlce, such as

a) a different processor design than the M1

b) different RAM modules that Samsung doesn't have in existence, so who and what? or, a different chassis design...

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#163
post #74

Earlier quoted context omitted.

The OS appears to partition the processors, like linux cpuset stuff, with low priority threads getting given to the efficiency cores, so you basically keep the low priority background stuff off the performant cores. How many is optimum is an interesting question, I would assume the apple peeps have a good idea and are on the money with this design.

it's not clear to me why the optimal number of efficiency cores wouldn't be zero on a desktop. why not just use the die area for additional performance cores? one or two full cores shouldn't have much effect on the thermal/power budget if they're just working on background tasks.

I suspect heat is a bigger problem than you're assuming, but also, you would want a similar architecture to simplify the os code.

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#165

Earlier quoted context omitted.

M1 mac pros were always going to come. Apple themselves announced that the next 2 years will be transition. I'd say if you purchased a Mac Pro, it's still the same. If you find yourself not having enough power, you bought the wrong machine to begin with (probably modern threadripper pro would be what you should have been looking for) If the computer satisfies all your performance needs, what use is it to "feel frustr…

> if you purchased a Mac Pro, it's still the same. If you find yourself not having enough power, you bought the wrong machine to begin with This is the reality really, if you actually wanted power then the Mac Pro just wasn't what you should have bought. Threadripper + Nvidia cards would take you way further for far less and with a clear sustainable upgrade path. Also really after the past 10 years of Apple's pro mov…

I'm currently grappling with an issue in my Linux VST development, where specifically Threadripper users are having issues. This is on Github and there are better people than me tackling it: it's an open source project so people can try everything they want.

So far the answer seems to be, there is no getting around these CPU issues through tailoring the compiler flags etc. and the best people can get is amelioration of the problem, not getting it back on par with normally inferior Intel chips. Again, the issue is that the Threadripper stuff is eating unreasonable CPU and the Intel stuff, normally not as good, is not doing that.

I suspect what you're looking at there is a CPU architecture that's getting optimized for specific conditions, which my plugins don't meet. There seems no fix other than 'you should be playing Mass Effect on this computer instead'.

I'm sure that it would destroy the Intel computer if you're doing that, but generalizing that to all conditions seems not justified.

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#166
post #46

It says the split for performance versus efficiency cores will be: - 20 total, 16 high performance, 4 efficiency - 40 total, 32 high performance, 8 efficiency Which is kind of interesting given that the 8 core M1 is split half/half at 4 high performance, 4 efficiency. Sounds like perhaps MacOS doesn't typically have more than 4 cores worth of low-priority work, regardless of the system size/workload?

That seems a bit weird to me. Many programs are hard to multithread but I'd expect that if any given program can make effective use of 8 threads it can probably keep scaling to 16 and 32. The hard part is getting from 1 to 2 and 2 to 4. So I'd expect that in most cases having more than 8 high performance cores doesn't make that much sense.

> it can probably keep scaling to 16 and 32

Bad assumption. It's pretty difficult to write a multithreaded program that scales up to 32 cores. You have to carefully avoid all sources of process-wide contention. The only cases where it is easy to just keep adding cores are where the units of independent work are overwhelmingly large compared to everything else, like video compression.

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#167
post #45

As someone who just invested in a Mac Pro late last year, I'm a bit frustrated. I wanted years for a modular design that I could keep and upgrade over a longer time only to find out I'll be forcefully phased out within 2 years.

everyone saw this coming, you can consider recouping your costs now

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#168
post #115
post #77

Earlier quoted context omitted.

Consider the use cases. The Mac Pro is a desktop, always plugged in and used for the power. The M1 is on a laptop running on a battery where efficiency is more important to improve the battery life.

So why put efficiency cores in the desktop processor at all?

[deleted]

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#169
post #36

40 cores? This thing will be dazzling.

Adding a bunch of tiny cores to an SOC is easy. What’s much harder is writing the software to make use of them.

Apple's cores are anything but tiny. The M1, a 4+4 processor, uses 16B transistors, approximately equal to a NVIDIA RTX 3070.

Re: Apple Readies MacBook Pro, MacBook Air Revamps

#170

Earlier quoted context omitted.

They used to. In ye olde dayes they were great about it.

When was that, the Mac II days?

Apple II :)

Jobs specifically hated that, and it was indeed the Mac II where Gassee and others pressured him into producing a Mac with more expandability.

Post reply on HN