Creating this page to more easily track and visualize what system/group/wave is being used where in the ~ipp/ippconfig/pantasks_hosts.input file. seem to recall was done before but cannot find ...

Node group summary:

• wave1 (w1): ipp008--021, 8 core, 24G
• wave2 (w2): ipp023--036, 8 core, 32G
• wave3 (w3): ipp037--053, 8 core, 24/32G
• wave4 (w4): ipp054--066, 12 core, 49G
• compute (c): ippc01-c19 -- many are ignored_, 8 core, 32G
• compute2 (c2): ippc20--c29, 12 core, 24G (c26-c28 49G, c29 73G)
• compute3 (c3): ippc30--c63, 12 core, 49G
• stare (s): stare00-04: 12 core, 97G
• stsci (st): stsci00-19, 12 core, 49G -- not to be used in processing

Other special (sub)groups:

• dvo/ignore: ipp004-007
• apache: ippc01-c09

• wave1_weak -- weak meaning cannot have full loads (i.e., lost CPU or other issue): ipp010-012,018
• wave2_weak: ipp023,027,028,029,032,033
• wave3_weak: ipp047
• compute3_weak:

• compute2_himem -- c2 w/ extra RAM: ippc26-c28, c29 (c29 typically out of processing for very deep stack tests)

testing 2014 nightly+LAP+staticsky

Want to balance for more staticsky progress now.

• ipptopsps also will not be running for a bit so can use more of the system.

pantasks	w1	w1w	w2	w2w	w3	w3w	w4	c	c2	c3	c3w	stare	comment
stdscience	5	2	4	2	4	3	4	2	2	2	3	0	100% use, LAP light, nightly, updates moder, N=200? (need >200)
stack	0	0	0	0	1	1	1	1	2	0	0	0	100% use, LAP/nightly heavy, N~80? (need >60)
summitcopy	0	0	1	1	1	0	1	0	0	0	0	0	nightly	need N>30
registration	1	0	1	1	1	0	1	0	0	0	0	0	nightly
distribution	0	0	1	1	1	0	0	1	0	0	0	0	nightly
pstamp	2	0	0	0	0	0	0	2	0	0	0	0	regular
cleanup	1	0	1	1	1	0	1	0	0	0	0	0	regular
publishing	0	0	0	0	0	0	0	1	0	0	0	0	nightly, light
ippsky/staticsky	0	0	0	0	0	0	1	0	1	3	0	4	100% use, LAP, heavy+very long running, N=127 (+20*80% for overloaded stare) ?
equiv. totals	x	x	x	x	x	x	x	x	x	x	x	x
replication	0	0	1	1	1	1	0	0	0	0	0	0	light load, not always in use -- should rebalance when in use
deepstack	0	0	0	0	0	0	0	0	0	2	0	0	heavy+very long running, not always in use, -2x c3 from other when is
detrend	1	0	1	0	1	0	1	0	0	0	0	0	light load, not always in use -- should rebalance when in use

Load level

• light = ~1 thread equiv, fairly quick runtime (x1)
• moder = ~1-4 thread, moderately fast runtime (x1-2)
• heavy = mostly 2-4 thread, longer runtime (x3-4)

When ipptopsps loaders not in use -- ipp045-ipp066 (half wave3+wave4), stare

• overloaded stare (+4x) nodes for staticsky

Cleanup add to stsci nodes?

---

late 2014

A reconfiguration once ipptopsps and loaders running full time.

• stare fully allocated to PSPS
• w1-4 reduced to account for extra load to data nodes

pantasks	w1	w1w	w2	w2w	w3	w3w	w4	c	c2	c3	c3w	stare	comment
stdscience	3	2	3	2	3	3	3	4	4	5	3	0
stack	0	0	0	0	2	1	2	2	2	2	0	0
summitcopy	0	0	1	1	1	0	1	0	0	0	0	0
registration	1	0	1	1	1	0	1	0	0	0	0	0
distribution	0	0	1	1	1	0	0	1	0	0	0	0
pstamp	2	0	0	0	0	0	0	2	0	0	0	0
update	0	0	0	0	0	0	0	1	1	0	0	0
cleanup	1	0	1	1	1	0	0	0	0	0	0	0
publishing	0	0	0	0	0	0	0	1	0	0	0	0
replication	0	0	1	1	1	1	0	0	0	0	0	0
deepstack	0	0	0	0	0	0	0	0	0	2	0	0
detrend	1	0	1	0	1	0	1	0	0	0	0	0
equiv. totals	x	x	x	x	x	x	x	x	x	x	x	x	ignoring repl, deepstack, detrend

---