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:53] hmeij07 [Funding Policy] |
cluster:189 [2020/01/11 18:12] hmeij07 [Priority Access] |
||
---|---|---|---|
Line 7: | Line 7: | ||
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 " | 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 " | ||
+ | |||
+ | The Advisory Group meets with the user base yearly in 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 users are contributing feedback on progress and problems. | ||
==== Structure ==== | ==== Structure ==== | ||
Line 33: | Line 35: | ||
* >3125 = 0.000048 | * >3125 = 0.000048 | ||
A cpu usage of 3,125,000 hours/year would cost $ 2,400.00 \\ | 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.\\ | ||
+ | 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 in the future with the TrueNAS/ZFS appliance (190 tb, 475 tb effective assuming a compression rate of 2.5x). a guide can be found here [[cluster: | ||
- | priority access policy | ||
- | 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 | ||
- | Script preempts nodes every 2 hours. | ||
+ | ==== 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 " | |
- | ===== Priority Access ===== | + | |
- | + | ||
- | 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 few Principles in this Priority Access Policy | There are few Principles in this Priority Access Policy | ||
Line 54: | Line 49: | ||
- 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. |