[c-nsp] Pix to Pix tunnel performance w/Windows File Sharing,>

[Hank Nussbacher]

Playing with MTU/MSS and other tweaks will only take you so far with 
performance issues for Windows File sharing.  That is why a slew of 
companies have been formed:

http://www.riverbed.com/
http://www.riverbed.com/industry/compare.html
"Some compression vendors offer TCP latency optimization as well. The 
difference is that Riverbed offers application level latency optimization. 
While TCP can be improved, the bottleneck in a latency-bound WAN is 
typically in the application's protocol (e.g. MAPI or CIFS), not in TCP. 
So, if you improve the way TCP behaves on a high latency link, you may not 
improve the performance of the application at all."

http://www.tacitnetworks.com/
http://www.tacitnetworks.com/docs/Whitepaper-WindowsOnTheWAN.pdf

http://www.actona.com/Index.html
[Bought out by Cisco and now in the Storage Networking BU]

http://www.disksites.com/
http://www.disksites.com/solution-overview.htm
Note the 100ms graphs on this page for open and save operations via CIFS/NFS.

Basically, CIFS is not meant for WAN consumption whether it be via tunnel 
or not.

Regards,
Hank