5 ms·

Wait, what? So the system was purposefully hindering everyone's productivity? Sounds more like a "I brought up production" story...

• mikewarot 5y ago
  No, it was just a bad configuration choice by the system administrator.
• exikyut 5y ago
  My guesstimated translation: some large number of those users were running compile jobs, which were running as background tasks instead of foreground tasks.
  • mikewarot 5y ago
    Yes, 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 ago
      resource starvation with a human element!