On 16 November 2010 02:06, Greg Sevart <[email protected]> wrote: > I'm speaking a little outside of my comfort zone, but based on my > understanding, LACP (802.3ad) generally doesn't provide any increase in > throughput for a single stream. The idea is to provide fault tolerance, and > provide more bandwidth for multiple streams over multiple hosts--but any > single stream is usually going to be using only one link. My understanding > is that most switches select which link in the bundle to use based on some > math on source MAC address. >
I understand that LACP provides redundacy and more multiple stream bandwidth from other PCs but I'm looking more for throughput between the NAS and the work machine. > > If your goal is to provide more bandwidth for a single stream (or even > multiple streams between the same two systems), 10Gb is going to be your > best bet--but it will be pricey. If you're only interested in speed between > your desktop and the fileserver, you could consider running a dedicated > link > between those two, and use some HOSTS trickery to ensure your traffic goes > down that dedicated link. > You're refferring to something like a VPN connection? > > If you're running Windows, you're also going to want to make sure that both > sides are SMB2 capable--ie: Vista/Server 2008 or newer. Whereas speeds over > about 50 or 60MB/s are uncommon (but not unseen) over SMB1, I regularly get > north of 115MB/s between SMB2-capable boxes, even over crummy home grade > switches and Realtek NICs. Most non-Windows SMB implementations are still > running SMB1, with SMB2 support still immature in projects such as SAMBA. > My HTPC runs W7 Ultimate and the NAS / file server runs Server 2008 R2. How do you make sure the connections are SMB2? This is done automatically, correct?
