Paul wrote:
> When I ran the transfer test, I got an average of 55MB/sec. The
> CPU on the laptop was flat out at 100%, while I think my desktop
> wasn't quite as heavily loaded. It might have gone faster, if
> the CPU clock rate was higher.
Which reminds me that one of the properties of the NIC device in Device
Manager is whether to optimize it for throughput or CPU usage. As I
recall when changing any properties for the NIC, you have to reboot for
them to be effected. When I changed the optimize property, my NIC
stopped working and I had to reboot. From what little I found online,
you set "optimize for throughput" if you mostly download and "optimize
for CPU" if you are running a server app on your host. Yet I also see
comments that it won't much affect network performance for home users
and only makes some difference on servers under heavy loads. With heavy
loads, you don't want the NIC to take a backseat to the CPU.
http://www.pcwintech.com/increase-network-performance
The article notes the "Optimize For" might be just an nVidia NIC
property. That's what I have and it defaulted to CPU for optimize. If
the optimize property is there for your NIC, you could try testing with
it set to Throughput instead of CPU.
Tweak #3 reminds me of something different in Windows Vista/7 regarding
TCP properties but damn if I can remember it now. I think it was called
something like "TCP Receive Window Auto-Tuning Level".
http://ttcshelbyville.wordpress.com/...twork-windows/
http://support.microsoft.com/kb/935400
http://support.microsoft.com/kb/947239