[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

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

531.0. "performance monitoring more than 64 nodes." by UTRTSC::DOCTER (Dik Docter) Thu Dec 22 1994 10:17

Hi,

A customer considers migrating from VCS to Polycenter Console Manager and at
the same time extend the number of monitored systems to more than 64.
They intend to use a VAXsation 4000-60 for this purpose, and wonder about memory
requirements.
I realize no hard figures can be given, because it all depends on the usage.

Does any of you have any experience with monitoring more than 64 nodes?
Will a 4000-60 be fast enough. Any estimates for the amount of memroy required?

Any comments will be welcome

Dik Docter
T.RTitleUserPersonal
Name
DateLines
531.1WOTVAX::ELLISMAre you all sitting too comfybold square on your botty? - Then wThu Dec 22 1994 11:0711
    There is a note very early on in the conference (before 20.*) that
    gives you memory requirements.
    
    as for processor speed, well it depends on how much work you want it to
    do, but my gut feel is that for a system that is not overloaded (that
    is a lot of console activity) 64 would be the maximum you want to go
    to. Usualy this will be more than adequate, but you have to remember
    that with Console Manager, you have to capacity plan for worst case
    scenarios - which is when you usualy need a console manager!
    
    Martin
531.2OPG::PHILIPAnd through the square window...Thu Dec 22 1994 11:2914
  By all means use the recommendations earlier in the conference (Note 7.1).

  Be aware however, that we can happily manage more than 64 systems on a 4000-60,
  we have done so ourselves with just such a system (it has 80Mb memory). Only
  when we start to run the interactive components (most notably the C3) does
  performance suffer because those interfaces are the most memory hungry, notice
  I said memory, because in all our testing, we have never really run out of CPU.

  So, if you are sizing, concentrate on Memory and IO (number of logging spindles).

Cheers,
Phil

531.3UTRTSC::DOCTERDik DocterFri Dec 23 1994 08:453
Thanks 

Dik