... and no, that's not 36 hours in…100,000 active hours
This evening our cluster achieved another small mile stone, 100,000 active computational hours, or put another way, all the current jobs running at the moment have consumed about 11.4 years of computation.
... and no, that's not 36 hours in…
... and no, that's not 36 hours in…
These nodes have been placed on hold and the reason for us doing this is so that we can 'drain' them of jobs prior to upgrading and patching. We prefer…