----- Originele e-mail -----
Van: "Christophe Varoqui" <christophe.varoqui@xxxxxxxxx>
Aan: "bart coninckx" <bart.coninckx@xxxxxxxxxx>
Cc: dm-devel@xxxxxxxxxx
Verzonden: Dinsdag 6 juli 2010 10:25:00 GMT +01:00 Amsterdam / Berlijn / Bern / Rome / Stockholm / Wenen
Onderwerp: Re: understanding of multipathing and speed
> routing points to the correct interface per network. Maybe my test
> (bonnie++)
>
> is not an appropriate one to show the difference in speed?
>
an interesting data point would be a perf run when iet target has only one target port on a bonded interface a multipath on client side.
And maybe the other combinations. Th eset combinations would be :
- client bonded, target not bonded
- client bonded, target bonded (i understand this is the scenario with good performance you reported earlier)
- client not bonded, target not bonded (perf expected from a single path in your testing)
- client not bonded, target bonded
the mixed setup would not be adequate for production as they require linked or single switch setups, but the information might help determine if the performance drop is due to multipath or iet multi-target.
Bye.
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
Christophe,
I have previously done no bonding in this setup, that was just to refer to how I would multipathing would behave speed wise when configured with round-robin, namely just like bonding does with round robin: the speed is almost doupled.
This is now a production machine, so juggling with bonding and non-bonding is somewhat difficult. I did do a tcpdump on both interfaces while doing a copy and there seems to be traffic on both interfaces while I copy a file, but the speed does not prove to get higher with interfaces available.
Would it matter if I experiment with rr-min-io? This is now set to 100.
Cheers,
Bart
> routing points to the correct interface per network. Maybe my test > (bonnie++) > > is not an appropriate one to show the difference in speed? > an interesting data point would be a perf run when iet target has only one target port on a bonded interface a multipath on client side. And maybe the other combinations. Th eset combinations would be : - client bonded, target not bonded - client bonded, target bonded (i understand this is the scenario with good performance you reported earlier) - client not bonded, target not bonded (perf expected from a single path in your testing) - client not bonded, target bonded the mixed setup would not be adequate for production as they require linked or single switch setups, but the information might help determine if the performance drop is due to multipath or iet multi-target. Bye.
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
