From: "J. Bruce Fields" <bfields@fieldses.org>
To: sfaibish <sfaibish@emc.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Performance results with exofs
Date: Mon, 7 Jun 2010 14:29:48 -0400 [thread overview]
Message-ID: <20100607182948.GF25257@fieldses.org> (raw)
In-Reply-To: <op.vdxxhfqsunckof@usensfaibisl2e.eng.emc.com>
>> 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?
- Have you tried any other workloads? (Perfectly reasonable
that simple write throughput would be the first thing to
check--I'm just curious.)
>>>
>>
>> - All tests over an *empty* filesystem.
>>
>>> [single client]
>>> 1 - osds 40MB
>>> 2 - osds 80MB
>>> 4 - osds 114MB (saturation point of the 1 Gbit link)
>>> 8 - osds 114MB
>>>
>>> [2 clients 8of8 osds]
>>> 226 MBs
>>>
>>> [4 clients 8of8 osds]
>>> 263 MBs
>>>
>>> [8 clients 8of8 osds]
>>> 252 MBs
>>>
>>> [1 clients 3of8 osds]
>>> 114 MBs
>>>
>>> [2 clients 3of8 osds *]
>>> 226 MBs
>>>
>>> [4 clients 3of8 osds *]
>>> 417 MBs
If each osd has a single gigabit interface, and you're striping to 3, of
them, isn't that 417/3 == 139 MB/s each?
(Oh, I see: you must be writing to a different file from each client,
hence you are using all osd's even if each client is only using 3?)
--b.
>>>
>>> [8 clients 3of8 osds]
>>> 405 MBs
next prev parent reply other threads:[~2010-06-07 18:29 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 [this message]
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
[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=20100607182948.GF25257@fieldses.org \
--to=bfields@fieldses.org \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sfaibish@emc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox