[Lustre-discuss] tcp network load balancing understanding lustre 1.8

[Mag Gam]

I second the responses.

Go with Native OS bonding, Linux in this case. Makes life so much easier...

Good luck


On Thu, May 7, 2009 at 8:20 PM, Isaac Huang <He.Huang at sun.com> wrote:
> On Thu, May 07, 2009 at 03:02:49PM -0700, Klaus Steden wrote:
>> ......
>> I didn't even touch Lustre bonding, because as you both remark, it's a
>> little convoluted. I spent a lot of time experimenting with Lustre over
>> 802.3ad (LACP) aggregated links using the Linux bonding driver, and my OSS
>> nodes produced very respectable to very good numbers. Across a pair of OSS
>> nodes each with 2 x GigE NICs, I was able to sustain ~ 350 MB/s write speed
>> when running sandbox tests, so it appears that although the LACP driver
>> doesn't balance a connection across multiple links (i.e. a 2 GigE LACP bond
>> doesn't give you 2 Gbit throughput for a single network I/O), the Lustre
>> implementation somehow manages to squeeze more data through the pipe.
>
> Probably because the Lustre TCP driver creates multiple connections
> between two end points, for different types of data.
>
> Thanks,
> Isaac
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>