From: sfaibish <sfaibish@emc.com>
To: "Benny Halevy" <bhalevy@panasas.com>,
"J. Bruce Fields" <bfields@fieldses.org>
Cc: "Boaz Harrosh" <bharrosh@panasas.com>,
"NFS list" <linux-nfs@vger.kernel.org>
Subject: Re: Performance results with exofs
Date: Tue, 08 Jun 2010 10:48:55 -0400 [thread overview]
Message-ID: <op.vdzkrtmqunckof@usensfaibisl2e.eng.emc.com> (raw)
In-Reply-To: <4C0DE93D.2050503@panasas.com>
Problem solved; I sent Bruce 2 relevant papers from CMU and FAST 2009.
/Sorin
On Tue, 08 Jun 2010 02:54:53 -0400, Benny Halevy <bhalevy@panasas.com>
wrote:
> On 2010-06-07 21:49, J. Bruce Fields wrote:
>> On Mon, Jun 07, 2010 at 09:41:29PM +0300, Boaz Harrosh wrote:
>>> On 06/07/2010 09:29 PM, J. Bruce Fields wrote:
>>>>>> On 06/07/2010 07:07 PM, Boaz Harrosh wrote:
>>>>>>> I did not yet publish the Document. It's stuck behind my
>>>>>>> dis-talent for
>>>>>>> writing and the pnfs bugs de jur.
>>>>
>>>> Untalented writing we can fix, as long as the details are there!
>>>>
>>>>>>>
>>>>>>> Basically all machines:
>>>>>>> - connected by a 1 GBit link.
>>>>>>> - All clients doing a dd write of 8GB file from /dev/zero
>>>>>>> - 3of8 is the special raid-groups arrangement of exofs && objlayout
>>>>>>> where out of 8 devices each file is striped over 3 devices in a
>>>>>>> round robin fashion. (*With a small dirty trick)
>>>>
>>>> Random stupid questions:
>>>>
>>>> - why do you think the 3of8 arrangement is scaling better than
>>>> the 8of8?
>>>
>>> It's a know problem with a network storage cluster. What happens is
>>> that with 8of8 all the clients exercise all of the nodes at the same
>>> time so they are clashing on the network.
>>
>> OK, so if two clients are both trying to send a stripe of data to the
>> same OSD data at the same time, absent a switch that could somehow
>> afford to queue up a full stripe-unit's worth of data, packets get lost?
>>
>> (Also, out of curiosity: do you know of any papers or documentation that
>> describe that problem in more detail?)
>>
>
> A good place to start would be
> http://www.pdl.cmu.edu/Incast/
>
> Benny
>
>> --b.
>> --
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Best Regards
Sorin Faibish
Corporate Distinguished Engineer
Network Storage Group
EMC²
where information lives
Phone: 508-435-1000 x 48545
Cellphone: 617-510-0422
Email : sfaibish@emc.com
next prev parent reply other threads:[~2010-06-08 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.vdxrrgf1unckof@usensfaibisl2e.eng.emc.com>
2010-06-07 16:07 ` Performance results with exofs Boaz Harrosh
2010-06-07 16:13 ` Boaz Harrosh
2010-06-07 17:28 ` sfaibish
[not found] ` <op.vdxxhfqsunckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-07 17:29 ` Boaz Harrosh
2010-06-07 17:34 ` sfaibish
2010-06-07 18:29 ` J. Bruce Fields
2010-06-07 18:41 ` Boaz Harrosh
2010-06-07 18:49 ` J. Bruce Fields
2010-06-08 5:26 ` Boaz Harrosh
2010-06-08 6:54 ` Benny Halevy
2010-06-08 14:48 ` sfaibish [this message]
[not found] ` <op.vdzkrtmqunckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-08 23:15 ` J. Bruce Fields
2010-06-07 18:43 ` Boaz Harrosh
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=op.vdzkrtmqunckof@usensfaibisl2e.eng.emc.com \
--to=sfaibish@emc.com \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox