3 ms·
The most likely issue is MacOs has scheduling issues. In Go, it's pretty trivial to do an experiment where you load a bunch of stuff into memory and have a cor
by foobiekr 5y ago
The most likely issue is MacOs has scheduling issues.
In Go, it's pretty trivial to do an experiment where you load a bunch of stuff into memory and have a core per thread race through it, basically doing stream, and if you do this the UI will start stuttering prior to going completely non-responsive. Similarly, on the m1 macs, with nothing more than writes to an SMB mount, you can cause the entire system to wedge [this is trivial to reproduce using rclone against a SMB mount]. There's no reason these should ever happen.
What can I say, I was curious if the advertised crazy levels of M1 pro memory bandwidth were genuine or conflating the all-in system-wide not-actually-visible-to-cores bandwidth hypothetically available.