Regulation procedures for allocated hours

In order to achieve a maximally constant usage of computation resources, GENCI and the three national computing centres (CINES, IDRIS and TGCC) have set up regulation procedures to be applied to projects which are under-consuming their allocated hours. The hours recuperated through these procedures will be redistributed to other projects (in supplementary resources granted during the year and allocations made during the second DARI session).

Two types of regulating procedures (annual and monthly) are carried out at IDRIS, as at the other two national centres, in function of the volumetric analysis of the total annual allocation of hours attributed to each project.

Allocation < 5M hours on Turing or < 1M hours on Ada (annual regulation)

Projects which obtained an allocation inferior to 5 million hours on the Turing machine or inferior to 1 million hours on the Ada machine, are subject to the following annual hours regulation procedure:

  • Projects which have used less than 30% of their allocation during the first 5 months of the period, could be subject to an adjustment modality resulting in the retraction of up to 40% of their total annual hours allocation. A warning message will be sent at the beginning of May to the managers of projects which have under-consumed. Project managers who furnish a well-argued justification of the under-consumption could be exonerated from the adjustment modalities. This justification must be sent to GENCI before end-May.
  • Project managers who have indicated before end-January their intention of not using their allocation until the second half of the year, could be exonerated from these measures if there is prior agreement from GENCI. This request must be exceptional and addressed to the IDRIS director.

Allocation ≥ 5M hours on Turing or ≥ 1M hours on Ada (monthly regulation)

For a given project P, at a given date d, we define the following terms:

  • Alloc(d) = the allocation of a project P obtained during the first or second DARI allocation session, plus (+) possible supplementary hours obtained by request during the year, minus (-) any hours retracted during previous months.
  • TMC(d) = Theoretical Monthly Consumption(d) = the sum obtained by dividing each of the allocations by its respective validity duration (12 months for the first DARI session, 6 months for the second session, variable durations for the supplementary requests), minus (-) the total sum of any hours retracted (divided by its respective validity duration, i.e. until the end of the year).
  • TC(d) = Theoretical Consumption(d) =TMC(t)dt between January 1 and d. This is the number of hours which should be consumed by date d if a project P consumes its hours with perfect regularity from the first to last day of the allocation validity.
  • Δ(d) = consumption(d) minus (-) TC(d). If Δ(d)<0, the project P is in under-consumption at date d.

For example, a project P obtains 1 200 000 hours at the first DARI session, followed by a retraction of 100 000 hours on March 15, then a new allocation of 400 000 hours at the second DARI session, plus a requested supplementary allocation of 100 000 hours on November 15 of the same year. The quantitative evolution of the allocation, theoretical monthly consumption and theoretical consumption of this project during the year is represented in the table and figure below:

1 Jan. to 14 March 15 March to 30 June 1 July to 15 Nov. 16 Nov. to 31 Dec.
Alloc 1 200 000 1 100 000 1 500 000 1 600 000
TMC 1 200 000 / 12
= 100 000
100 000 - 100 000 / 9,5
= 89 474
89 474 + 400 000 / 6
= 156 140
156 140 + 100 000 / 1.5
= 222 807
TC TMC(t)dt

Projects which obtained a total allocation of ≥ 5M hours (on Turing) or ≥ 1M hours (on Ada), are subject to the following hours regulation procedure (applied monthly):

  • At date d (corresponding to the 15th of each month), we calculate Δ(d).
  • If the project does not show under-consumption (i.e. Δ(d) > 0), or shows only slight under-consumption (i.e. Δ(d) > -TMC(d)), it means that the project is regularly consuming the resources which were attributed to it and, therefore, is not behind time. In this case, no action is taken.
  • If the project shows under-consumption which is between one and two times its TMC(d) (i.e. -2*TMC(d) < Δ(d) < -TMC(d)), a warning e-mail is sent to the project manager informing him/her of the under-consumption.
  • If the project shows under-consumption which is superior to two times its TMC(d) (i.e. Δ(d) < -2*CTM(d)), then a volume of hours corresponding to its TMC(d) is retracted from its total allocation. An e-mail is sent to the project manager informing him/her of the under-consumption and the resulting retraction of hours.

In practical application, a project which obtains hours during the first allocation session (Sept-Oct) and begins usage on January 1, will not have hours retracted on January 15. In case of under-consumption, warning messages would be sent on February 15. The first retraction of hours would not take place before March 15.