Interactive/Compute Servers

From CS Support Wiki
Revision as of 16:07, 14 July 2005 by Ajb5d (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Interactives

viper, mamba, cobra, adder 
They are 360MHz UltraSPARC II systems with 1548Mb RAM and 2G of swap. These are not to be used for long-running jobs or jobs with very large memory needs. Typically the machine in your office will be assigned to either mamba or cobra. Viper is reserved for Faculty and Staff use. When logging in from outside, using the same machine you use in your office will help to more evenly disperse the computing load. If you don't have an office, just pick one and use it consistently. If the interactive server you normally use is down, you are free to use one of the others.

Compute Nodes

The department operates many 'compute servers.' These machines are tailored to run very large, compute-intensive jobs well. They have the most virtual memory, the fastest CPUs, and the additional benefit of having few interactive jobs competing for compute cycles.

The following policies govern all machines designated as compute servers:

Interactive sessions on compute servers should be kept to a minimum. 
Running a long FrameMaker session on one of these compute servers is an inappropriate activity. We have provided interactive servers and workstations for that kind of "everyday" computing. On the other hand, it is appropriate to do big compiles on these machines, and minor editing activity between compilations is a perfectly reasonable thing to do.
No person should have more than two jobs running at the same time on any given compute server or more than four jobs total on all compute servers. 
The rationale for this guideline is that when too many jobs get into the job mix, they compete for system resources, which can significantly reduce the throughput rate for everyone.
Rules were meant to be broken. 
We should not allow the existence of these guidelines to inhibit their entrepreneurial violation in responsible ways. For example, if you come in to work at 4:00am and see that altair is unused and you start up 4 big jobs, that's fine. Remember not to go away and leave them running throughout the day.

Solaris

General Purpose Compute Servers

whirlwind, archive
Sun Fire280R Server with 2 750Mhz processors 4 Gb of RAM and 6 Gb of Swap running Solaris 8
edvac 
Sun Enterprise E3500 with 4 400Mhz 2 Gb of RAM and 4 Gb of swap running Solaris 8
larc, stretch, colossus 
UltraSPARC E250 with 1 450 MHz processor, 1 Gb of RAM, and 2 Gb of swap running Solaris 8

Limited Use Compute Servers