It was noticed because of it's CPU usage. It seems most people think "that was lucky". It wasn't lucky, it was inevitable. It happened to be noticed by someo

It was noticed because of it's CPU usage. It seems most people think "that was lucky". It wasn't lucky, it was inevitable. It happened to be noticed by someone doing benchmarking, but there is another category of machines out there it would hit hard: low end VM's running an ssh server. I've had my low end VM's hit by exactly the same thing the postgres benchmarker saw, but on these box's it isn't just annoying. There are so many ssh logins happening the OOM killer comes out to play but these ssh logins are tiny so it tends to kill the real stuff you've got the box doing, like web serving. A 2 or 3 fold increase in CPU would suddenly bring a lot of VM to their knees. At least thousands of them. It would be noticed.