I just started playing with Network Render this weekend and finally got it working. Made a few obvious mistakes in setting it up but seems to work good now.
I have 2 PCs (athlon 64 3000+ and XP 2000+) running on 100 Mbps network, so CPUs are bottle neck. Using Task Manger, I see periodic bursts of at about 25% networking activity, with a 75% utiilization during the stitch at the end. CPU performance flatlines at 100% between the network spikes. I sort of doubt that the disk drive is the culprit. If I had fast enough CPU such that Ididn't see 100% utilization, then I would know there is a bottleneck somewhere else.
So, 10K rpm raptors or RAID for improving render time and network render? I suspect not noticable - maybe cut a 4 hour render to 3hrs 45 minutes?
I haven't gotten that answer yet. I am coming off V4, and was glad to get NR up and running. I have the video files on the older machine so serving those to the newer one bogs it down I suppose. Don't know that I have an optimum configuration either. Also, NR is good for AVI, not so good for MPG due to licenses of the MainConcep codec, so you have to take that into account. I'll try a couple cases and see what happens. Maybe look at the rendet test going on in the X2 thread.
I did a test case that is cpu intensive. 20 still photos, taken on Canon S50, 5mp. 5sec on the time line with 2s transition. The transitions really eat up the cpu cycles. I use event pan & scan to fit into 16:9 window, pan diagonally and then blow up to full screen on each one. Lots of MIPs. My system is not yet optimal, but here's what I get:
This makes sense as if I belive the AMD performance numbers, a "5000+" processor would take 5.09. There is about a 15 sec stick at the end.
Watching Task Manager Network Performance, I see 2% - 3% utilization with periodic spikes to 25%. So this test case is definitely CPU bound with little network rendering overhead.
2nd case: 3:00 minutes of DV w/audio. 7 cuts. No transitions, no pan & zoom, just plain vanilla frame copies. I only have 1 hard drive in the Athlon 64, so those numbers are probably a little slower.
Athlon 64 3000+ Foreground 0:56 (cpu at 10% - 15% utilization)
Athlon 64 3000+ Net.Render 0.36 (cpu at 50% - 80% utilization)
A64 3K + AXP 2K ....................... 1.16 (lots of time stitching)
Net: this aligns with what has been said here before: CPU intensive tasks that can render to AVI benefit from network rendering. Othewise......