[Networker] What does good LTO3 performance look like?

I'm backing up four streams of small files from a four-way FujitsuPW450 (equivalent to roughly a Sun V440) with a pair of DotHillSanNet II arrays running ZFS.

The storage node is a Sun V240 with an ADIC 100 LTO3 libraryattached, the networker node is another V240 with the indexes held oninternal disks using ZFS.

The storage node and the networker node are at one end of 30 miles ofGigE, the storage at the other. The GigE is essentially dedicated.

Everything's Solaris 10.latest, everything's Networker 7.3.3. Theobvious FSS niceties have been configured and the backup processesare all in their own projects with plenty of shares. The machinesare all otherwise idle.

I'm seeing about 200GB/hour (ie 55MB/sec, or ~50% of the networkbandwidth).


I'm not at all unhappy, and this is fine performance for me.

I'm just curious to know what the limiting factor is and if there'sanything obvious I could do to raise the performance a bit. This ismore about learning than about needs.

nsrmmd on the storage node is the obvious candidate, as it'sconsuming ~40% of a processor and making ~5K system calls persecond. Is it possible to raise the overall blocking factor to makemore efficient use of the CPU?


ian

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 with 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