Re:Apple M1 Ultra Meanings and Consequences
by pantulis on Monday March 14, 2022 @12:03PM
(#30674068)
Isn't running multiple single-threaded workloads at the same time also a case for better performance with more cores? So even for basic tasks having more cores is better (although maybe not that cost-efficient)
Re:Apple M1 Ultra Meanings and Consequences
by zaptrem on Tuesday March 15, 2022 @12:06PM
(#30687054)
Running lots of cores at a low speed can be more efficient than one core at turbo speed.
Re:Apple M1 Ultra Meanings and Consequences
by katbyte on Monday March 14, 2022 @02:31PM
(#30676167)
only if those workloads are very CPU intensive, and the ones that are should probably be parallelized as much as possible anyway.
Re:Apple M1 Ultra Meanings and Consequences
by BolexNOLA on Monday March 14, 2022 @06:35PM
(#30679390)
Sort of related: Adobe creative cloud is the most bloated, CPU-inefficient system I’ve ever had the displeasure of working with as a professional editor. I get FCPX is apple’s NLE but the render times smoke premier in comparison and CC in general is just way too busy in the background.
> Your average user is going to prefer double the clock rate of your processors to doubling the number of processors.
I disagree. The reality is that these days people are running multi-threaded workloads even if they don't know it. Running a dozen chrome tabs, Slack, Teams, Zoom, some professional tools like IDE's, Adobe creative suite, etc. adds up very quickly to a lot of processes that can use a lot of cores.
[1] https://browser.geekbench.com/mac-benchmarks