The new Mac Pro finally arrived in mid-December, though demand quickly outstripped supply. 'Can't innovate, my ass,' Schiller pointedly said at WWDC, in rebuttal to jibes that Apple innovation was adrift. Gone was the old aluminum Mac Pro, to be replaced by a sleek, dark gray cylindrical computer. That prompted Apple CEO Tim Cook to break from long-standing company tradition and essentially confirm that Apple engineers were indeed working on an update to the Mac Pro.Ĭonfirmation about the new Mac Pro came at the 2013 Worldwide Developers Conference (WWDC), when Apple's senior vice president of worldwide marketing, Phil Schiller, previewed Apple's new Pro desktop, announcing it would ship late in the year and showing off a radical new design in a dramatic movie trailer. Despite upgrades to numerous other models, the Mac Pro saw few changes for several years, leaving anxious Mac users in fear that Apple's flagship desktop computer would die entirely and prompting them to launch petitions seeking more information about Apple's plans. XCode) do utilize the high performance cores even for a longer time.Until mid-2013, the future of Apple's Mac Pro seemed to be in doubt. I also flagged the dispatch items with proper qos but that didn’t change anything. userInteracive up that didn’t help either. I even tried to set up the queue with qos set to. After a few seconds of running the high performance cores are obviously not utilized any more. I have read the Apple docs „Optimize for Apple Silicon with performance and efficiency cores“ and double checked that the dispatch queue for the iterations is set up properly: let simQueue = DispatchQueue.global(qos. Investigating a little bit further I noticed that at the start of the simulation all 8 cores of the M1 Mac are filled up properly but after a few seconds only the 4 high efficiency cores are used any more.

Mac mini, M1 8-core, Big Sur macOS 11.2, native ARM Mac mini, M1 8-core, Big Sur macOS 11.2, Rosetta2

6 cores mac mini faster 8 core mac pro