This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
cluster:189 [2020/01/11 17:34] hmeij07 |
cluster:189 [2020/01/11 21:12] hmeij07 |
||
---|---|---|---|
Line 3: | Line 3: | ||
===== Structure and History of HPCC ===== | ===== Structure and History of HPCC ===== | ||
+ | |||
+ | As promised at the CLAC HPC Mindshare event at Swarthmore College Jan 2020. Here is the Funding and Priority Policies with some context around it. | ||
==== History ==== | ==== History ==== | ||
- | In 2006, 4 Wesleyan | + | In 2006, 4 Wesleyan |
+ | |||
+ | The Advisory Group meets with the user base yearly during the reading week of the Spring semester (early May) before everybody scatters for the summer. At this meeting, the hpcadmin reviews the past year, previews the coming year, and the user base are contributing feedback on progress and problems. | ||
==== Structure ==== | ==== Structure ==== | ||
- | The Wesleyan HPCC is part of the **Scientific Computing and Informatics Center** ([[https:// | + | The Wesleyan HPCC is part of the **Scientific Computing and Informatics Center** ([[https:// |
- | The QAC has an [[https:// | + | The QAC has an [[https:// |
+ | ==== Funding Policy ==== | ||
- | Add scheme 2016 2019 | + | After an 8 year run of the HPCC, and a drying up of grant opportunities at NSF, it was decided |
- | Passwd line count 25 coll 200 class | + | |
- | 5 year review with provost link to paper (honors theses) | + | |
- | funding | + | |
- | 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 | + | Several months later a pattern emerged. The Provost would annually contribute $25K if the HPC user base raised $15K annually. That would amount |
- | contrib scheme contrib code ... | + | |
- | | + | |
- | 3x gpu vs cpu. | + | |
- | Script preempts nodes every 2 hours. | + | |
+ | In order for the HPC user base to raise $15K annually, CPU and GPU hourly usage was deployed. A dictionary is maintained listing PIs and their members (students majors, lab students, grads, phd candidates, collaborators, | ||
+ | Here is 2019's queue usage [[cluster: | ||
- | ===== Priority Access ===== | + | Contribution Scheme for 01 July 2019 onwards\\ |
+ | Hours (K) - Rate ($/CPU Hour)\\ | ||
+ | * 0-5 = Free | ||
+ | * > | ||
+ | * > | ||
+ | * > | ||
+ | * > | ||
+ | * > | ||
+ | A cpu usage of 3,125,000 hours/year would cost $ 2,400.00 \\ | ||
+ | A gpu hour of usage is 3x the cpu hourly rate.\\ | ||
- | This page will describe | + | We currently have about 1,450 physical cpu cores, 60 gpus, 520 gb of gpu memory and 8,560 gb cpu memory provided by about 120 compute nodes and login nodes. Scratch spaces are provide local to compute nodes (2-5 tb) or over the network via NFS (55 tb). Home directories are under quota (10 tb) but these will disappear |
+ | |||
+ | |||
+ | ==== Priority Policy ==== | ||
+ | |||
+ | 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 few Principles in this Priority Access Policy | There are few Principles in this Priority Access Policy | ||
Line 44: | Line 51: | ||
- 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. | - 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 community resource |
The first principle implies that all users have access to the new resources immidiately when deployed. Root privilege is for hpcadmin only, sudo privilge may be used if/when necessary to achieve some purpose. The hpcadmin will maintain the new resource(s) while configuration(s) of new resource(s) will be done by consent of all parties involved. Final approval by the Advisory Group initiates deployment activities. | The first principle implies that all users have access to the new resources immidiately when deployed. Root privilege is for hpcadmin only, sudo privilge may be used if/when necessary to achieve some purpose. The hpcadmin will maintain the new resource(s) while configuration(s) of new resource(s) will be done by consent of all parties involved. Final approval by the Advisory Group initiates deployment activities. |