Re: [Networker] Slow index browsing - additional
2003-07-28 08:13:56
At DR we had (10) 250Mhz in a e6000. We have similar problems in Orlando with
a e6500 with (10) 400Mhz cpus and 12 gigs of memory. I figured the nsrd ps was
single-threaded, how about nsrmmdbd? The sad thing, NetWorker is the only
non-system resource running on this system! This is the first diaster reovery
test where I have been in charge of the acutal restores and not just the
rebuilding of systems and I was very disappointed with how NetWorker ran. If
we can not restore all our data at the same time (with in reason) in the event
of a actual Disaster, this product worthless. It seems NetWorker is not
scalable and we have gone as far as we can with this product.
More thoughts please.
Steve
*******************************************
Steve Paige
UNIX System Administrator
407-355-6819 Desk
407-929-6483 Mobile
steve.paige AT chep DOT com
-----Original Message-----
From: Davina Treiber [mailto:treiber AT HOTPOP DOT COM]
Sent: Monday, July 28, 2003 6:03 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Slow index browsing - additional
On Mon, 28 Jul 2003 09:16:35 +0200, Riaan Louwrens
<riaanl AT SOURCECONSULTING.CO DOT ZA> wrote:
>I would like to jump onto the back of this question and ask whether there
>are any "utilities" for Unix / Solaris etc. We as well have a 480R box that
>seems to only use 1 of the 2 processors. Is there a way to "force"
Networker
>to use a second (i.e. 3rd / 4th - 10th) processor ?
>
>I know from all the guides and diswcussions that Legato is NOT single
>threaded (allegedly), the performance tuning guide does not really say
>anything helpfull at all (disk and tape write speeds tests are 100%). I
>guess performance tuning / debugging on the various OS's are only gained
>through experience ...
This has been discussed fairly recently on the list.
NetWorker as a whole product is not single-threaded, however the nsrd
process is. nsrd can often be the bottleneck, and can be seen to take up
100% of one CPU while others are idle. Over the years, Legato have improved
the efficiency of nsrd, the latest improvement being the splitting of the
res files in 6.2 and 7.0. There is still more to do IMHO.
Because of nsrd being the bottleneck, you will usually find that for a
NetWorker server, faster CPUs is much preferable to more CPUs. A large NW
server will be struggling with 250MHz CPUs on a Sun box, however many of
them you have.
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
|
|