1494
Comment:
|
1651
|
Deletions are marked like this. | Additions are marked like this. |
Line 24: | Line 24: |
Three options: |
|
Line 30: | Line 28: |
It is not common but a server could have multiple local volumes (think of it as having multiple disks) so check if there is an /lfs/local/1 if you're running out of space. |
Infolab QuickStart
Infrastructure
The InfolabComputeServersStats lists our big memory servers. These are first come first serve (nobody is managing the resources). If you are on a tight deadline or you feel that somebody is hogging the machine talk to them or talk to your local sysadmin.
You can access this machines by logging in via ssh with your CSID. Here's an example:
~$ ssh tommy@madmax5 tommy@madmax5's password: Last login: Sun Oct 4 10:54:11 2015 from whale.stanford.edu tommy@madmax5:~$
Using Windows? Use PuTTY or Cygwin.
Which server to pick?
The one that's feeling lonely (shows zero or little utilization). As a general rule of thumb Chris' students should go for raidersX machines and Jure's students should go for madmaxX machines.
Storage options
Storage option |
Mount point |
Good for |
Speed |
Backed up? |
Your home directory |
/afs/cs/u/tommy |
Stuff that matters, e.g. results, code |
Not really |
Daily |
Local hard disk |
/lfs/local/0 |
Temporary files, intermediate results |
Around 150 MB/s |
No |
Network storage |
/dfs/scratchX |
Datasets, things you need accessible across multiple servers |
Up to 450 MB/s, but shared! |
No |
It is not common but a server could have multiple local volumes (think of it as having multiple disks) so check if there is an /lfs/local/1 if you're running out of space.
Long running sessions
Compute cluster