4 ms·
Back in the day when computers were slow (like, megahertz slow) you could do this with code execution to help with debugging. If you played with a piece of code
by btbuildem 3y ago
Back in the day when computers were slow (like, megahertz slow) you could do this with code execution to help with debugging. If you played with a piece of code long enough you'd get very familiar with the patterns (they were tones, not just ticks) and it was easy to tell when something was off / different.
- deleted 3y ago[deleted]
- seabass-labrax 3y agoAnd later, when computers weren't so slow but still required multiple fans and HDDs (using real metal discs!) you got an auditory indication of resource utilisation. I do wonder what we'll say in the future when we look back at computers from this time - perhaps it won't be so much an auditory clue, but the subtle feel of one's phone getting warm in your hand when it is running all cores at full clock?
- CapsAdmin 3y agoWith my speaker setup I always had slight gpu coil whine from gpu usage. This has helped me a few times to figure out if the gpu is doing any work at all when trying to figure out why something in ie pytorch is slow.