abstract:darwin:earlyaccess

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

abstract:darwin:earlyaccess [2021-04-26 10:02] – [Memory] pdwabstract:darwin:earlyaccess [2021-04-27 16:21] (current) – external edit 127.0.0.1
Line 92: Line 92:
 A list of installed software that IT builds and maintains for DARWIN users can be found by [[abstract:darwin:system_access:system_access#logging-on-to-caviness|logging into DARWIN]] and using the VALET command ''vpkg_list''. A list of installed software that IT builds and maintains for DARWIN users can be found by [[abstract:darwin:system_access:system_access#logging-on-to-caviness|logging into DARWIN]] and using the VALET command ''vpkg_list''.
  
-Documentation for all software is organized in alphabetical order on the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> under [[software:software|Software]].+Documentation for all software is organized in alphabetical order on the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> under [[software:software|Software]]. There will likely not be a details by cluster for DARWIN, however referring to Caviness should still be applicable for now.
  
 There will **not** be a full set of software during early access and testing, but we will be continually installing and updating software.  Installation priority will go to compilers, system libraries, and highly utilized software packages. Please DO let us know if there are packages that you would like to use on DARWIN, as that will help us prioritize user needs, but understand that we may not be able to install software requests in a timely manner.  There will **not** be a full set of software during early access and testing, but we will be continually installing and updating software.  Installation priority will go to compilers, system libraries, and highly utilized software packages. Please DO let us know if there are packages that you would like to use on DARWIN, as that will help us prioritize user needs, but understand that we may not be able to install software requests in a timely manner. 
Line 137: Line 137:
 </code> </code>
  
-Now we can use ''salloc'' or ''sbatch'' to submit an interactive or batch job respectively.  See DARWIN [[abstract:darwin:runjobs:runjobs|Run Jobs]], [[abstract:darwin:runjobs:schedule_jobs|Schedule Jobs]] and [[abstract:darwin:runjobs:job_status|Managing Jobs]] wiki pages for more help about Slurm including how to specify resources and check on the status of your jobs.+Now we can use ''salloc'' or ''sbatch'' as long as a [[abstract:darwin:runjobs:queues|partition]] is specified as well to submit an interactive or batch job respectively.  See DARWIN [[abstract:darwin:runjobs:runjobs|Run Jobs]], [[abstract:darwin:runjobs:schedule_jobs|Schedule Jobs]] and [[abstract:darwin:runjobs:job_status|Managing Jobs]] wiki pages for more help about Slurm including how to specify resources and check on the status of your jobs.
  
 <note important> <note important>
Line 143: Line 143:
 </note> </note>
  
-<note tip>It is a good idea to periodically check in ''/opt/templates/slurm/'' for updated or new [[technical:slurm:darwin:templates:start|templates]] to use as job scripts to run generic or specific applications, designed to provide the best performance on DARWIN.</note>+<note tip>It is a good idea to periodically check in ''/opt/shared/templates/slurm/'' for updated or new [[technical:slurm:darwin:templates:start|templates]] to use as job scripts to run generic or specific applications, designed to provide the best performance on DARWIN.</note>
  
-==== Memory ====+See [[abstract/darwin/runjobs/|Run jobs]] on the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> for detailed information about the running jobs on DARWIN and specifically [[abstract:darwin:runjobs:schedule_jobs#command-options|Schedule job options]] for memory, time, gpus, etc.
  
-The table below provides the usable memory values available for each type of node currently available on the DARWIN. 
- 
-^Node type                  ^Slurm selection options                                        ^RealMemory/MiB  ^RealMemory/GiB^ 
-|Standard/512 GiB           |%%--%%constraint='standard'                                    |    499712|       488| 
-|Large Memory/1 TiB         |%%--%%constraint='large-memory'                                |    999424|       976| 
-|Extra-Large Memory/2 TiB   |%%--%%constraint='xlarge-memory'                                 2031616|      1984| 
-|nVidia-T4/512 GiB          |%%--%%constraint='nvidia-t4' %%--%%gpus=tesla_t4:               499712|       488| 
-|nVidia-V100/768 GiB        |%%--%%constraint='nvidia-v100' %%--%%gpus=tesla_v100:<N>          737280|       720| 
-|amd-MI50/512 GiB           |%%--%%constraint='amd-mi50' %%--%%gpus=amd_mi50:             |    499712|       488| 
-|Extended Memory/3.73 TiB   |%%--%%partition=extended-mem %%--exclusive%%                        |    999424|       976| 
- 
-The **Extended Memory** node is not accessible via Slurm constraint or gres, but instead specifying the partition ''lg-swap'' and ''exclusive'' options.  This allows only one user on the node at a time thereby making all swap space accessible for multiple jobs running on that node at once, sharing the swap; but no other user can be on it during that time. 
 ===== Help ===== ===== Help =====
  
  • abstract/darwin/earlyaccess.1619445763.txt.gz
  • Last modified: 2021-04-26 10:02
  • by pdw