Edison Big-Job Discount and Low Charge Class Retirement
February 27, 2017
by Rebecca Hartman-Baker
The big job discount on Edison will be reduced from 40% to 20% this Wednesday, March 1, 2017, and be removed entirely when Cori goes into production, currently planned for July 1.
Also this Wednesday, NERSC will retire the "low" charge class, which granted users a 50% discount in exchange for low priority. When a repo is out of time, its jobs will automatically be placed in the low-priority scavenger QOS and will be able to run free of charge if resources become available.
We expect that both of these changes will shorten wait times on Edison. The big-job and low-priority discount have the indirect effect of manufacturing additional allocated time. If a user has an allocation of one million NERSC hours and uses it entirely for large job runs, then they have consumed 1.67 million NERSC hours worth of resources while being charged for only one million. Likewise, one million NERSC hours of low-priority jobs consumes two million NERSC hours worth of resources. This inflation of allocation creates a situation where there are effectively more NERSC hours available to spend than can be delivered, resulting in a very crowded queue.
We originally implemented the big job discount as an enticement, to encourage users to run large jobs. However, given the level of adoption (more than half of NERSC hours spent on Edison were large jobs last year), the incentive was a success and can now be retired.
When we first implemented the low-priority job discount, we did not have a means for users whose allocations were low to run. This was seen as a way to stretch those last few allocation hours. Now that we do have a means for users to run after their allocation is used up, we no longer need the low-priority job discount.
All users, and especially those running big jobs, are encouraged to apply to the KNL Early Access Program. Jobs on the Cori KNL nodes will run free of charge through the end of June. Access will not be denied due to poor application performance; the purpose of the application process is to make sure that users are not unpleasantly surprised when running on the KNL nodes.