@artman @steipete But… but… they promised!!

@tapi @steipete Well, they sort of kept their promise. If you don't do WMO then you'll see a 50% decrease in compile times. But who doesn't do WMO?

@artman Since when developers are Pros? Real pros make 8k videos of a guy eating a beagle, let's be real.

@theandreamazz Since Swift demanded us to compile with super-computers I guess.

@slava_pestov @vrutberg Not really. LLVM still executes in parallel and modules that don’t depend on each other are compiled in parallel.

@artman @steipete Not really. My project compilation times are 400 seconds on MBP vs 192 seconds on iMac Pro.

@artman Are we talking about the 5k monster? I saw something similar with a MBP 2015 vs 2017. But to be fair, multitasking while building was better in the 2017 model

@artman Is this for real? I expected big gains out of the iMac Pro

@artman @Javi That seems to be in line with

@artman That seems rather counter intuitive - any idea why?

@artman MBP tests indicate that you’ll get almost no Swift Xcode compilation performance gains compared to a bucket of boiled horse piss

@artman @steipete xcode is probably just bad at using multiple cores. I guess apple will now make it a priority to fix that.

@artman @steipete There is no big difference in CPU speeds between them. Where you will see a bigger difference (apart of multicore tasks) will be long running tasks where a laptop will have to throttle down for thermal reasons and desktop computer can continue working full speed.

@artman @steipete Reasons like this are why I bought a 2010 12 core Mac Pro and put in a RAID 0 AHCI Samsung SSD array on an Amfeltec Squid board. Under hyperthreading, there are 24 cores to compile and a throughput of up to 5 GB/s off of the drive.

@artman 😱😱😱😱

@artman Source?