Heh.  NetWorker is multithreaded, but in a very heavyweight way.  Generally, 
rather than spawning a thread, it will spawn a process when it needs to.  This 
is improving, but multithreading in NW can be considered as nsrd being thread1, 
nsrmmdbd being thread2, nsrindexd as thread3 etc.
 
Generally, if one CPU is busy then nsrd is trying to figure out which volume to 
send save sessions to and on which drive.  If you constantly have incoming 
saves waiting to be serviced through multiple pools or DDS, then nsrd will keep 
a processor warm trying to figure out where to direct it.
 
Cheers,
 
Stuart.

________________________________

From: EMC NetWorker discussion on behalf of Teresa Biehler
Sent: Wed 20-Sep-06 16:54
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] multi-threaded/single-threaded



We've been doing some monitoring on our NetWorker server.  We find that
one of four CPUs is VERY busy.  I'm guessing this means that something
within NetWorker is single-threaded.  Is there information somewhere
about which of the daemons are single-threaded and which are
multi-threaded?



If this information is environment specific, we're running NW 7.2.2 on
Solaris 10 on a V880.



Thanks.

Teresa


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER