4 ms·

> ...I run compiles for 20 seconds max now. Not really enough time for throttling to kick in. Still, fantastic performance even if just in bursts. https://twi

• marricks 6y ago
  He ran it to the point of throttling and it slowed down less than the gains, about 25% slower than fastest speeds. Also brought up the very good point that if you compile (and do other tasks) fast enough, you don't actually need to throttle so the point can, in the real world, be moot.
• deleted 6y ago
  [deleted]
• ogre_codes 6y ago
  If your workload never requires more than 20 seconds of compiling, then throttling will never be an issue. I suspect for most modern developers, short, frequent compiling is a more common use-case than 10m+ builds. For video editors and other pros, it's different, but since Apple's CPU offloads a lot of the video & audio processing to secondary processors, I don't think that will be an issue either.
• tomaskafka 6y ago
  Here is The Verge's test with 30 minute Cinebench loop. It seems that from now on the only difference between Air and Pro is that Air throttles down to about 70 % in sustained mode while Pro's cooling keeps up. (Also, even thermally throttled M1 destroys my current 4C/8T 4 GHz Haswell desktop, which is beyond powerful for everything I need.) https://twitter.com/keff85/status/1328740865926459400 https://twitter.com/keff85/status/1328740865926459400