| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
Customer is running PCM 1.6-201 on Alpha1000 128MB
monitoring 80 systems. Expect to be running 12 C3
displays from the Alpha to different displays.
We have done the BYTLM, PRCLM, PGFLQUO tuning, and removed all extraneous
software (Pathpig, etc), and as we add systems we are seeing
a pretty significant slowdown.
They are shadowing the logfile disk (RZ29). VMS 6.2
My questions are:
(a) what is a good rule of thumb for memory required?
I think they need more, but "buy more memory" typically
needs a justification. Looking for 64MB for VMS +
"n" MB for each system monitored.
(b) would not shadowing the logfile disk help?
Sandra Mereos
CSC Internals & Drivers
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1349.1 | SNOFS1::ELLISS | Are you all sitting too comfybold square on your botty? - Then we'll begin | Thu Aug 01 1996 19:57 | 12 | |
Hi, read note 7.1 for memory configuration guidelines For logging of data, shadowing will not help as shadowing actually slows down write time (Speeds up Read time), as it has to write to two spindles every time, whereas it can choose which spindle to read from. I would recommend using either a combination of RAID0 & 1, which gives you maximum protection and throughput (Parallel writes) as well as easy management, or distribute the logging of various systems across different spindles - manual, but effective. Shaun | |||||