Our great sponsors
-
XcodeBenchmark
XcodeBenchmark measures the compilation time of a large codebase on iMac, MacBook, and Mac Pro
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The main issue is that the test he did focused on doing one thing at a time, so let's say you are compiling an Xcode project, all the LightRoom / etc programs are swapped, but they aren't actively working and therefore you don't run into much danger of thrashing the memory. Also, the singular tasks he did aren't super memory intensive either. For example, the Xcode Benchmark test (GitHub link) doesn't really look that intensive just from cursory looks at it (and also considering an M1 MacBook can build it in 130 seconds). If you want an intensive workout for Xcode you should compile say WebKit which takes 20 minutes on an M1, and would properly stress both CPU and memory usage and allow you to see the effect.
Also check out the (Gorgonia)[https://github.com/gorgonia/gorgonia] project if you're not familiar with ML in Go, it's a lot of fun and our basis (with contributions back of course =D)