In that guy’s defense, you as a user have EVERY right to be pissed if your machine thrashes so badly that your system stops responding in an era of 32 Gb of RAM and 8 core CPUs.
We had a mainframe that, because user IO was a higher priority than background jobs, would slowdown the server by a user treating the F5 button like he was in a competition playing Track and Field in the televised 100m dash event while waiting for work to populate. That system was well over 32gb of ram with many more than 8 cores.
In that guy’s defense, you as a user have EVERY right to be pissed if your machine thrashes so badly that your system stops responding in an era of 32 Gb of RAM and 8 core CPUs.
Especially if the OS or the program just says “fuck you! Wait until it solves itself or get fucked” instead of “the problem is XYZ”
We had a mainframe that, because user IO was a higher priority than background jobs, would slowdown the server by a user treating the F5 button like he was in a competition playing Track and Field in the televised 100m dash event while waiting for work to populate. That system was well over 32gb of ram with many more than 8 cores.
We had to talk to him.