During day up to 4 active networker/nwadmin sessions.  During night, only one.  
Always horribly behind on mounts (they seem to not be priority) and single 
400Mhz Ultrasparc II (III?) always pegged just running nsrd.  FYI - 500 clients 
= 8TB per night.  10x9840 drives per e4500 storage node (8x400) - 2 storage 
nodes.  4x9840 and 4x400 on e450 master.  
--Ted

And in response to Andrew McGeorge, our bottleneck is DEFINITELY the available 
processor cycles to nsrd on a single 400Mhz.  nsrd may bottleneck itself at 
higher cpu clock cycles.....I wish I had that problem


-----Original Message-----
From: Byron Servies [mailto:bservies AT PACANG DOT COM]
Sent: Friday, June 27, 2003 5:39 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] 7.0 Experience


On June 27, 2003 at 14:12, Reed, Ted G II [ITS] wrote:
>
> How many clients were you running that a 3GHz processor had issues?  I have 
> 500 on a 4x400MHz Sun master with two e4500 storage nodes.  In that 
> environment, one cpu is pegged about 22 hours a day and nsrd is VERY much our 
> performance bottleneck.  Do you have any thoughts about how much (percentage) 
> the load dropped after moving to 7.x and the more efficient DB style?

On a related note: a common way to load up a nsrd is to have
too many monitoring programs running at once.  nsrd responds
to all status requests from programs like nsrwatch, nwadmin,
etc., as well as initial save and recover requests.  The
windows nwadmin in particular is notorious for requesting status
from nsrd more often than it should.

Anyway, if you have a number of administrators who are all
monitoring backup performance, you are actually driving up
the nsrd load significantly.  This may not be your problem,
but it is certainly something to look at.

Byron

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=