Symphony Compute Nodes
2010 compute nodes (i7)
GG.04
cn101cn102cn103cn104cn105cn106cn107cn108cn109cn110
cn111cn112cn113cn114cn115cn116cn117cn118cn119cn120
2008 compute nodes (Core2)
GG.04
cn121cn122cn123cn124cn125cn126cn127cn128cn129cn130
cn131cn132cn133cn134cn135cn136cn137cn138cn139cn140
 
Large compute nodes
GG.04cn191cn192
2008 compute nodes (Core2)
M1.64
cn241cn242cn243cn244cn245cn246cn247cn248cn249cn250
cn251cn252cn253cn254cn255cn256cn257cn258
cn259cn260
cn261cn262cn263cn264cn265cn266cn267cn268cn269cn270
cn271cn272cn273cn274cn275cn276cn277cn278cn279cn280
cn281cn282cn283cn284cn285cn286cn287cn288cn289cn290
 
Linux werewolf nodes (i5)
R6
 
MacOS werewolf nodes (i3)
GB04
 
SG.16
 
SG.17
 
SG.18

What the Graphs are Telling You

Nodes counted as "Running - Fully Loaded" are in use and do not have enough spare capacity to accommodate a further job.

Nodes counted as "Running - Spare Capacity" are running. They may be idle or may be running one job but have enough spare capacity to accommodate another.

Nodes counted as "Offline - Power Saving" have been marked as currently unavailable by our software which shuts down computers which aren't in use. These nodes are made available again if new jobs are submitted which could use them. Werewolf nodes are not affected by Symphony's power management.

Unavailable nodes are really not available to the scheduler. This is usually for one of three reasons: