Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ICAEN.UIOWA.EDU!dbfunk
From: dbfunk@ICAEN.UIOWA.EDU (David B Funk)
Newsgroups: comp.sys.apollo
Subject: Re:  Apollo SR10 Registry Performance
Message-ID: <8910210538.AA02105@icaen.uiowa.edu>
Date: 21 Oct 89 05:06:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Iowa Computer Aided Engineering Network, University of Iowa
Lines: 31

WRT posting  <114@bnrgate.bnr.ca>

>	Our site has approximately 440 Apollos on ethernet running sr10.1.
>	The Apollos are setup to run BSD4.3 unix exclusively. AEGIS is not
>	installed. We are experiencing some difficulties with registry nodes
>	being excessively overworked and occassionally melting down.  

I agree with all that Paul Anderson said <46574bed8.000f088@caen.engin.umich.edu>
and would add:

1)  "rgyd" can be a memory hog. It likes to keep the whole data base in
    memory and can use a lot. On our system (3000+ accounts) a "rgyd"
    uses about 6 Mb (based on a "ps agux"). It accounts for
    a lot of page faults on a system that has 8 Mb of memory (I hate
    to think of what it would to to a 4 Mb system :-). If possible, run
    it on a system that has plenty of RAM (particularly your master rgyd).
    Don't run it on the same node as other memory hungry daemons. EG put
    rgyd & glbd on different nodes.

2)  If you have too many rgyds then your master rgyd will spend a lot of
    time (cpu & network) making sure that all the slaves stay in sync.
    A registry change (new account, password chage, shell change, etc)
    must be distributed to all the slaves.

3)  There is a bug in the sr10.0 & sr10.1 rgyd implementation that can cause
    problems when your rgyds are left up for long periods of time on a system
    that is active. We have 3000+ accounts and do "cvtrgy"s daily. We've found
    that we have to reboot the master rgyd node at least once a month. This
    is supposed to be fixed at sr10.2.

Dave Funk