From: Joao Eduardo Luis <joao.luis@inktank.com>
To: "Chen, Xiaoxi" <xiaoxi.chen@intel.com>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
femi anjorin <femi.anjorin@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Ross Turk <ross@inktank.com>
Subject: Re: Ceph Production Environment Setup and Configurations?
Date: Tue, 29 Jan 2013 11:34:48 +0000 [thread overview]
Message-ID: <5107B3D8.8060504@inktank.com> (raw)
In-Reply-To: <6F3FA899187F0043BA1827A69DA2F7CC5E93B4@SHSMSX102.ccr.corp.intel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB2312, Size: 2166 bytes --]
On 01/29/2013 11:25 AM, Chen, Xiaoxi wrote:
> [The following views only behalf of myself, not relate with Intel..]
> Looking forward for the performance data on Atom.
> Atom perform badly in Swift, but since Ceph is slightly efficient than Swift, it must be better.
> I have some concern about weather Atom can support such high throughput( you have 16 disks, assuming 50MB/s per disk, you would like to have 50*16 *2(include journal write)=1600MB/s ,together with corresponding network throughput, say 10GbE. The total IO throughput seems too high for Atom. Baidu (www.baidu.com) use Arm based storage node(not using ceph,but their own DFS), a node with a quad-core Arm together with 4 disks, and a 2U box can put up to 6 nodes, the 6 nodes share a 10Gb NIC. Although Atom is different with Arm, but you can take Baidu as a reference.
>
>
> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Gandalf Corvotempesta
> Sent: 2013Äê1ÔÂ29ÈÕ 17:25
> To: femi anjorin
> Cc: ceph-devel@vger.kernel.org; Ross Turk
> Subject: Re: Ceph Production Environment Setup and Configurations?
>
> 2013/1/29 femi anjorin <femi.anjorin@gmail.com>:
>> CPU - Intel(R) Atom(TM) CPU D525 @ 1.80GHz
>
> Atom? For which kind of role ?
> --
> 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
> N§²æìr¸yúèØb²X¬¶Ç§vØ^\x7f)Þº{.n\x7f+·z]z÷¥{ay\x7f\x1dÊÚ\x7f,j\a¢f£¢·hàz\x7f\x1e®w¥¢\x7f\f¢·¦j:+v¨wèjØm¶\x7f\x7f\a«êçzZ+ùÝ¢j"ú!tml=
>
FWIW, Wido had been testing Ceph on Atoms a while back. I don't know
what conclusions he reached, or even if he has already reached any
conclusions at all. I, for one, would be really interested in knowing
how well (or how poorly) Atoms deal with Ceph.
Maybe Wido can share some thoughts on this one? :-)
-Joao
--
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
next prev parent reply other threads:[~2013-01-29 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPhYxPwK+wM1pBpaf7zXM-L6PagcKiQ_v07MXypRGrxj4oQZtw@mail.gmail.com>
2013-01-29 3:30 ` Fwd: Ceph Production Environment Setup and Configurations? femi anjorin
2013-01-29 9:24 ` Gandalf Corvotempesta
2013-01-29 11:25 ` Chen, Xiaoxi
2013-01-29 11:34 ` Joao Eduardo Luis [this message]
2013-01-29 13:40 ` Mark Nelson
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=5107B3D8.8060504@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=femi.anjorin@gmail.com \
--cc=gandalf.corvotempesta@gmail.com \
--cc=ross@inktank.com \
--cc=xiaoxi.chen@intel.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.