This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
cluster:189 [2020/01/10 19:50] hmeij07 created |
cluster:189 [2020/01/11 17:34] hmeij07 |
||
---|---|---|---|
Line 1: | Line 1: | ||
\\ | \\ | ||
**[[cluster: | **[[cluster: | ||
+ | |||
+ | ===== Structure and History of HPCC ===== | ||
+ | |||
+ | ==== History ==== | ||
+ | |||
+ | In 2006, 4 Wesleyan qfaculty members approached ITS with a proposal to centrally manage a whigh performance computing center (HPCC) seeding the effort with an NSF grant (about $190K). ITS offered 0.5 FTE for a dedicated " | ||
+ | |||
+ | ==== Structure ==== | ||
+ | |||
+ | The Wesleyan HPCC is part of the **Scientific Computing and Informatics Center** ([[https:// | ||
+ | |||
+ | The QAC has an [[https:// | ||
+ | |||
+ | |||
+ | Add scheme 2016 2019 | ||
+ | Passwd line count 25 coll 200 class | ||
+ | 5 year review with provost link to paper (honors theses) | ||
+ | funding policy | ||
+ | priority access policy | ||
+ | add VA questions | ||
+ | user base stats, annual meeting, spring reading week | ||
+ | 2019 queue usage stats link | ||
+ | adv group details, administrative | ||
+ | hpcc stats cpu cores, gpus, mem, hdd (rough) link to guide | ||
+ | latest deployment: nvidia gpu cloud on premise (docker containers) link | ||
+ | |||
+ | Add funding model | ||
+ | contrib scheme contrib code ... | ||
+ | Links to hist use. Usage 2019. | ||
+ | 3x gpu vs cpu. | ||
+ | Script preempts nodes every 2 hours. | ||
+ | |||
+ | |||
===== Priority Access ===== | ===== Priority Access ===== | ||
Line 6: | Line 39: | ||
This page will describe the Priority Access Policy in place at the current time (Jan 2020) for the HPCC. This policy was put in place about 3 years ago to deal with the issues surrounding new monies infusions from for example new faculty " | This page will describe the Priority Access Policy in place at the current time (Jan 2020) for the HPCC. This policy was put in place about 3 years ago to deal with the issues surrounding new monies infusions from for example new faculty " | ||
- | There are two main Principles in this Priority Access Policy | + | There are few Principles in this Priority Access Policy |
- | - Contributions, | + | - Contributions, |
- Priority access is granted for 3 years starting at the date of deployment (user access). | - Priority access is granted for 3 years starting at the date of deployment (user access). | ||
+ | - Only applies to newly purchased resources which should be under warranty in the priority period. | ||
The main objective is to build an HPCC for all users with no (permanent) special treatment of a subgroup. | The main objective is to build an HPCC for all users with no (permanent) special treatment of a subgroup. | ||
Line 17: | Line 51: | ||
The second principle grants priority access to certain resource(s) for a limited time to a limited group. The same PI/users relationship will be used as is used in the CPU Usage Contribution scheme. Priority access means if during the priority period the priority members jobs go into pending mode for more than 24 hours the hpcadmin will clear compute nodes of running jobs and force those pending jobs to run. | The second principle grants priority access to certain resource(s) for a limited time to a limited group. The same PI/users relationship will be used as is used in the CPU Usage Contribution scheme. Priority access means if during the priority period the priority members jobs go into pending mode for more than 24 hours the hpcadmin will clear compute nodes of running jobs and force those pending jobs to run. | ||
- | All users should be aware this may happen so please checkpoint your jobs with a checkpoint interval of 24 hours. Please | + | All users should be aware this may happen so please checkpoint your jobs with a checkpoint interval of 24 hours. Please |