All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig Dunwoody <cdunwoody@graphstream.com>
To: "Aleš Bláha" <ales-76@seznam.cz>
Cc: cdunwoody@graphstream.com, ceph-devel@lists.sourceforge.net
Subject: Re: [OLD ceph-devel] Hardware-config suggestions for HDD-based OSD node?
Date: Mon, 29 Mar 2010 15:05:24 -0700	[thread overview]
Message-ID: <2853.1269900324@n20.hq.graphstream.com> (raw)
In-Reply-To: Your message of "Mon, 29 Mar 2010 17:46:49 +0200." <20100329174649.f9d79f2b.ales-76@seznam.cz>


Hello Ales, 

Thank you for the additional suggestions.  It will be interesting
to see the similarities and differences between hardware configs that
work best for Lustre, and those that end up working best for Ceph.

Craig Dunwoody
GraphStream Incorporated

ales writes:
>Sure raw numbers for a hardware are often very impressive, but
>it is up to the software to squeeze the performance out of it.
>Experimenting is always the best way to find out, but you can search
>the web to get the picture. I suggest taking a look at Lustre
>setups - the architecture is very similar, they also use mostly
>of-the-shelf componenst. Apparently the common Lustre OSD is rather fat
>- plenty of disks divided into several RAID groups, very much like the
>X4500. Then againg, HPC people are mostly focused on
>streaming writes, so if your application differs then your point of
>diminishing returns might be elsewhere.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

  reply	other threads:[~2010-03-29 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 22:36 Hardware-config suggestions for HDD-based OSD node? Craig Dunwoody
2010-03-29  0:29 ` Martin Millnert
2010-03-29  1:15 ` Gregory Farnum
2010-03-29  1:48   ` Craig Dunwoody
2010-03-29  5:18 ` ales-76
2010-03-29 13:00   ` Craig Dunwoody
2010-03-29 15:46     ` Aleš Bláha
2010-03-29 22:05       ` Craig Dunwoody [this message]
2010-03-29 21:26 ` [OLD ceph-devel] " Sage Weil
2010-03-29 22:54   ` Craig Dunwoody

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=2853.1269900324@n20.hq.graphstream.com \
    --to=cdunwoody@graphstream.com \
    --cc=ales-76@seznam.cz \
    --cc=ceph-devel@lists.sourceforge.net \
    /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.