login : waltz
sp-overall : 6
t3e-overall : NaAn
pvp-overall : 7
pdsf-overall : NaAn
sp-uptime : 7
t3e-uptime : NaAn
pvp-uptime : 7
pdsf-uptime : NaAn
sp-wait : 3
t3e-wait : NaAn
pvp-wait : NaAn
pdsf-wait : NaAn
sp-queues : 5
t3e-queues : NaAn
pvp-queues : NaAn
pdsf-queues : NaAn
sp-interactive : 2
t3e-interactive : NaAn
pvp-interactive : NaAn
pdsf-interactive : NaAn
sp-disk : 4
t3e-disk : NaAn
pvp-disk : NaAn
pdsf-disk : NaAn
sp-procsused : 512
t3e-procsused : 
pvp-procsused : 1
psdf-procsused : 
sp-procsneed : 1024
t3e-procsneed : 
pvp-procsneed : 1
pdsf-procsneed : 
sp-comm : My main complaint is that this 2000+ supercomputer is being
used in a broad user based time-share envionment as 10-20
clusters. The factional use with > 512 (0r even >256) is to small.
We are paying dearly for unsued connectivity and the system is not
being used properly. For the same hardware price, NERSC could
be a \"cluster center\" offering 3-5x more FLOP\'s per year. The users
need a computer center with more capacity (not capabiity). If we
had a \"cluster center\", a machine like seaborg could be freed up
the it\'s best use....codes that need and can used > 1024 (or2048)
ps.   The expansion ratio (turn-around time/actual run time) has
much improved this year (generally below 2 and used to be often
> 10); but next year seaborg is going to be overloaded again
t3e-comm : With the demise of the T3E seaborg loading is going to get worse.
pvp-comm : With the demise of the PVP, the loading of seaborg is going to get
worse....there is now no place to run the vector codes
pdsf-comm : 
hpss-overall : NaAn
hpss-uptime : NaAn
hpss-reliable : NaAn
hpss-perf : NaAn
hpss-response : NaAn
hpss-interface : NaAn
hpss-comm : 
newton : NaAn
escher : NaAn
server-comm : 
page_no : 6