3 ms·
I've seen reports of pops/crackles in digital audio mixing/synthesis applications being fixed by disabling hyperthreading. This makes some sense if hyperthreadi
by ploxiln 6y ago
I've seen reports of pops/crackles in digital audio mixing/synthesis applications being fixed by disabling hyperthreading. This makes some sense if hyperthreading can sometimes cause extra latency for some threads to get real CPU work done, which is hard for the OS to strictly control. There have been a few different ways to disable hyperthreading on macbooks over the years, but recently Apple offers a good way (to mitigate recent Intel CPU vulnerability corner-cases for the paranoid): https://support.apple.com/en-gb/HT210108 https://support.apple.com/en-gb/HT210108
- derefr 6y ago> This makes some sense if hyperthreading can sometimes cause extra latency for some threads to get real CPU work done, which is hard for the OS to strictly control. Threads requiring hard real-time responsiveness can (and do) request to be marked as such by the scheduler. And the OS is certainly aware of what hyperthreads-presenting-as-cores belong to which physical cores, and uses this information in scheduling. So I'd find it implausible that any modern OS (esp. one that already had good DAW support) doesn't already have logic to try to keep the other hyperthreads of a core on which a hard-realtime thread is running, as uncontended as possible, by either not scheduling, or very conservatively scheduling (i.e. "early" pre-empting) anything on that hyperthread. I have a feeling it's something much more arcane. Maybe a hitch generated by the core switching "licenses" due to an AVX512 instruction.
- happymellon 6y agoI can get pops and crackles in Spotify. It isn't hyperthreading, which has never been an issue before, on any platform. The audio subsystem has been fucked up in some way.