3 ms·
It was 1985, I was in a VAX computer lab with about 40 other people typing on the VT100 terminals... I ran a program to compute something, and forgot that I ha
by mikewarot 5y ago
It was 1985, I was in a VAX computer lab with about 40 other people typing on the VT100 terminals... I ran a program to compute something, and forgot that I had bumped my priority wayyy up... everything in the room stopped, even the line printer, everyone went ohhhhhh.
10 seconds later, my program finished... and everything snapped back to life.
Another time, I walked into a different, bigger lab, with 100 terminals... snooped around the system, saw that the compiler queue had about 40 minutes of entries... bumped the first one up a bit (the queue was set to lower priority than any of the users, which was a mistake)... it finished in 2 seconds, instead of 2 minutes...
15 minutes later, the queue was empty, 30 minutes after that the room was empty, because everyone had gotten their work done.
- mrleinad 5y agoWait, what? So the system was purposefully hindering everyone's productivity? Sounds more like a "I brought up production" story...
- mikewarot 5y agoNo, it was just a bad configuration choice by the system administrator.
- exikyut 5y agoMy guesstimated translation: some large number of those users were running compile jobs, which were running as background tasks instead of foreground tasks.
- mikewarot 5y agoYes, because the system administrator, in his great wisdom made the compiler a batch job, but left the default priority way too low, below all interactive task. Which meant the users had to wait around, so the labs would always end up full of logged in users, frustrated that the system was so darn slow.
- jhanschoo 5y agoresource starvation with a human element!