User name Ole Hansen
Log entry time 12:34:58 on June 3,2004
Entry number 124572
This entry is a followup to: 124534
Regarding adaql2: Looks like et_start is eating 220M of vmem. Run top and hit "M" to sort by memory usage. The overall memory usage on adaql2 does not look too bad. Only 32M in swap. Most usage occurs due to caching/buffering of the CODA files as they are written to disk and served to analysis jobs. adaql2 is fine for DAQ, but too weak to be a fileserver to half a dozen clients. We should upgrade.