Infolab wiki
Differences between revisions 4 and 5
|
Size: 869
Comment:
|
Size: 887
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Infrastructure overview = | = infolab QuickStart = == Infrastructure overview == |
| Line 11: | Line 13: |
| tommy@madmax5:~$ uptime 00:53:00 up 134 days, 19:21, 9 users, load average: 33.06, 33.05, 33.00 tommpy@madmax5:~$ |
tommy@madmax5:~$ |
| Line 16: | Line 16: |
| {{{#!wiki note As a general rule of thumb Chris' students should go for raidersX machines and Jure's students should go for madmaxX machines. }}} |
=== Which server to pick === |
| Line 20: | Line 18: |
| = Storage options = | 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 == |
infolab QuickStart
Infrastructure overview
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:~$
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
Long running sessions
Compute cluster