Reminder -- Allocation Changes starting Oct 1

Posted: September 30, 2013

There are two major changes regarding allocation usage with the start of the new quarter tomorrow:

First, Kingspeak will no longer be run in frecycle mode. Freecycle jobs can still run, but they will be preembtable.

Second, there has been a change in allocation policy. Instead of having individual allocations for Kingspeak and for Ember, there will be one combined pool of allocation that will be used on these two clusters. Ember jobs will be charged the number of core hours (1 SU = 1 CPU-core-wall-clock-hour), whereas Kingspeak jobs will be charged 1.5 times the number of core hours (1.5 SU = 1 CPU-core-wall-clock-hour), to account for the faster speed of the nodes of this cluster. Groups with existing Ember allocations will have the amount adjusted to conform with the new metric of 1 SU = 1 CPU-core-wall-clock-hour and these awards can be used on either Ember or Kingspeak.