User Tools

Site Tools


techstaff:aicluster

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
techstaff:aicluster [2020/11/11 11:40] kauffmantechstaff:aicluster [2020/12/10 12:57] – [Batch] kauffman
Line 5: Line 5:
 Feedback is requested: Feedback is requested:
  
- #ai-cluster Discord channel or email Phil Kauffman (kauffman@cs dot uchicago dot edu).+ [[https://discord.gg/ZVjX8Gv|#ai-cluster Discord channel]] or email Phil Kauffman (kauffman@cs dot uchicago dot edu).
  
 Knowledge of how to use Slurm already is preferred at this stage of testing. Knowledge of how to use Slurm already is preferred at this stage of testing.
Line 12: Line 12:
 The information from the older cluster mostly applies and I suggest you read that documentation: https://howto.cs.uchicago.edu/techstaff:slurm The information from the older cluster mostly applies and I suggest you read that documentation: https://howto.cs.uchicago.edu/techstaff:slurm
  
 +
 +====== Infrastructure ======
 +Summary of nodes installed on the cluster
 +
 +===== Computer/GPU Nodes =====
 +  * 6x nodes
 +    * 2x Xeon Gold 6130 CPU @ 2.10GHz (64 threads)
 +    * 192G RAM
 +    * 4x Nvidia GeForce RTX2080Ti
 +
 +  * 2x nodes
 +    * 2x Xeon Gold 6130 CPU @ 2.10GHz (64 threads)
 +    * 384G RAM
 +    * 4x Nvidia Quadro RTX 8000
 +
 +  * all:
 +    * zfs mirror mounted at /local
 +      * compression to lz4: Usually this has a performance gain as less data is read and written to disk with a small overhead in CPU usage.
 +      * As of right now there is no mechanism to clean up /local. At some point I'll probably put a find command in cron that deletes files older than 90 days or so.
 +
 +===== Storage =====
 +
 +  * ai-storage1:
 +    * 41T total storage
 +    * uplink to cluster network: 2x 25G
 +    * /home/<username>
 +      * We intend to set user quotas, however, there are no quotas right now.
 +    * /net/projects: (Please ignore this for now)
 +      * Lives on the home directory server.
 +      * Idea would be to create a dataset with a quota for people to use.
 +      * Normal LDAP groups that you are used to and available everywhere else would control access to these directories. e.g. jonaslab, sandlab
 +
 +  * ai-storage2:
 +    * 41T total storage
 +    * uplink to cluster network: 2x 25G
 +    * /net/scratch: Create  yourself a directory /net/scratch/$USER. Use it for whatever you want.
 +    * Eventually data will be auto deleted after X amount of time. Maybe 90 days or whatever we determine makes sense.
 +
 +  * ai-storage3:
 +    * zfs mirror with previous snapshots of 'ai-storage1'.
 +    * NOT a backup.
 +    * Not enabled yet.
 +
 +
 +====== Login ======
 +There are a set of front end nodes that give you access to the Slurm cluster. You will connect through these nodes and need to be on these nodes to submit jobs to the cluster.
 +
 +    ssh cnetid@fe.ai.cs.uchicago.edu
 +
 +  * Requires a CS account.
 +
 +==== File Transfer ====
 +You will use the FE nodes to transfer your files onto the cluster storage infrastructure. The network connections on those nodes are 2x 10G each.
 +
 +=== Quota ===
 +  * By default users are given a quota of 20G.
  
 ====== Demo ====== ====== Demo ======
Line 67: Line 123:
 </code> </code>
  
 +==== Notes on CUDA_VISIBLE_DEVICES ====
 +CUDA_VISIBLE_DEVICES: Displays relative gpu device number available to you. 
  
 +  * This variable should NOT be modified. Ever.
 +  * Relative means that if you requested one gpu it will show up as 0. Even if all other gpus on the server are being used by others.
  
  
 +===== Fairshare/QOS =====
 +By default all usage is tracked and charged to a users default account. A fairshare value is computed and used in prioritizing a job on submission.
  
- +Details are being worked out for anyone that donates to the clusterThis will be some sort of tiered system where you get to use higher priority when you need it
-====== Storage ====== +You will need to charge an account on job submission ''%%--account=<name>%%'' and most likely select the priority level you wish to use and that you are allowed to use: ''%%--qos=<level>%%''
- +
-  /net/scratch: +
-     Create  yourself a directory /net/scratch/$USER. Use it for whatever you want. +
- +
-  /net/projects: (Please ignore this for now) +
-    Lives on the home directory server. +
-    Idea would be to create dataset with a quota for people to use+
-    Normal LDAP groups that you are used to and available everywhere else would control access to these directories. +
-    e.g. jonaslab, sandlab +
- +
- +
-Currently there is no quota on home directories. +
- +
-homes and scratch each connected via 2x 25G. Both are SSD only so the storage should be FAST. +
- +
- +
-Each compute node (nodes with gpus) has a zfs mirror mounted at /local +
-I set compression to lz4 by default. Usually this has a performance gain as less data is read and written to disk with a small overhead in CPU usage. +
-As of right now there is no mechanism to clean up /local. At some point I'll probably put a find command in cron that deletes files older than 90 days or so.+
  
  
Line 107: Line 150:
 </code> </code>
  
 +
 +===== Jupyter Notebook Tips =====
 +==== Batch ====
 +The process for a batch job is very similar.
 +
 +jupyter-notebook.sbatch
 +<code>
 +#!/bin/bash
 +unset XDG_RUNTIME_DIR
 +NODEIP=$(hostname -i)
 +NODEPORT=$(( $RANDOM + 1024))
 +echo "ssh command: ssh -N -L 8888:$NODEIP:$NODEPORT `whoami`@fe01.ai.cs.uchicago.edu"
 +. ~/myenv/bin/activate
 +jupyter-notebook --ip=$NODEIP --port=$NODEPORT --no-browser
 +</code>
 +
 +Check the output of your job to find the ssh command to use when accessing your notebook.
 +
 +Make a new ssh connection to tunnel your traffic. The format will be something like:
 +
 +''%%ssh -N -L 8888:###.###.###.###:#### user@fe01.ai.cs.uchicago.edu.edu%%''
 +
 +This command will appear to hang since we are using the -N option which tells ssh not to run any commands including a shell on the remote machine.
 +
 +Open your local browser and visit: ''%%http://localhost:8888%%''
 +==== Interactive ====
 +  - ''%%srun --pty bash%%'' run an interactive job
 +  - ''%%unset XDG_RUNTIME_DIR%%'' jupyter tries to use the value of this environment variable to store some files, by defaut it is set to '' and that causes errors when trying to run juypter notebook.
 +  - ''%%export NODEIP=$(hostname -i)%%'' get the ip address of the node you are using
 +  - ''%%export NODEPORT=$(( $RANDOM + 1024 ))%%'' get a random port above 1024
 +  - ''%%echo $NODEIP:$NODEPORT%%'' echo the env var values to use later
 +  - ''%%jupyter-notebook --ip=$NODEIP --port=$NODEPORT --no-browser%%' start the jupyter notebook
 +  - Make a new ssh connection with a tunnel to access your notebook
 +  - ''%%ssh -N -L 8888:$NODEIP:$NODEPORT user@fe01.ai.cs.uchicago.edu%%'' using the values not variables
 +  - This will make an ssh tunnel on your local machine that fowards traffic sent to ''%%localhost:8888%%'' to ''%%$NODEIP:$NODEPORT%%'' via the ssh tunnel. This command will appear to hang since we are using the -N option which tells ssh not to run any commands including a shell on the remote machine.
 +  - Open your local browser and visit: ''%%http://localhost:8888%%''
  
/var/lib/dokuwiki/data/pages/techstaff/aicluster.txt · Last modified: 2021/01/06 16:11 by kauffman

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki