All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Madhusudhana U <madhusudhana.u.acharya@gmail.com>,
	ceph-devel@vger.kernel.org
Subject: Re: Throughput increase by LACP bonding
Date: Tue, 03 Jul 2012 13:50:49 +0200	[thread overview]
Message-ID: <4FF2DC99.2090000@widodh.nl> (raw)
In-Reply-To: <20120703105624.GA10864@hmsreliant.think-freely.org>



On 03-07-12 12:56, Neil Horman wrote:
> On Tue, Jul 03, 2012 at 10:07:16AM +0200, Wido den Hollander wrote:
>>
>>
>> On 03-07-12 09:42, Madhusudhana U wrote:
>>> Hi all,
>>> I am trying to increase the throughput in the cluster by enabling
>>> LACP on both in clients and all ceph cluster nodes. Each client and
>>> ceph nodes has two 1G Ethernet interface which I want to aggregate
>>> and make it 2G. LACP has been configured at switch side too. But even after
>>> the configuration, I am not seeing any through put increase in ceph tell osd
>>> bench command and also dd. They are taking the same amount as earlier. I am
>>> constantly seeing around 100MB/sec throughput in both DD and ceph bench
>>> commands. Can someone suggest me how i can increase the throughput of the
>>> cluster ? Below are my configurations.
>>
>> Can you verify if both NIC's are actually doing something? Use
>> bwm-ng for example?
>>
>> Wido
>>
> I would imagine they aren't, as the output hash function for 802.3ad trunking is
> based on source and destination address, so if your test just writes from a
> single client to a single OSD, it will just use one link.

He mentioned "both in clients and ..." So I figured he had multiple clients.

But yes, you are right about the hashing. He should be using multiple 
clients to use both NIC's in the Ceph nodes.

Wido

> Neil
>
>>>
>>> 	No of OSD's 	: 5
>>> 	No of MON's 	: 3
>>> 	No of MDS's	: 2
>>> 	Linux Kernel	: 3.4.4
>>> 	Ceph version	: 0.47.3
>>>          Hard disks      : 2x160G SAS drives (raid 0 configuration)
>>>          CPU             : Intel(R) Xeon(R) Quad CPU E5506  @ 2.13GHz
>>>          Memory          : 6G
>>>
>>> Thanks
>>> __M
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>


  reply	other threads:[~2012-07-03 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  7:42 Throughput increase by LACP bonding Madhusudhana U
2012-07-03  8:07 ` Wido den Hollander
2012-07-03 10:56   ` Neil Horman
2012-07-03 11:50     ` Wido den Hollander [this message]
2012-07-03 15:18 ` Gregory Farnum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FF2DC99.2090000@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=madhusudhana.u.acharya@gmail.com \
    --cc=nhorman@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.