From: Craig Dunwoody <cdunwoody@graphstream.com>
To: Martin Millnert <martin@millnert.se>
Cc: cdunwoody@graphstream.com, ceph-devel@lists.sourceforge.net
Subject: Re: Hardware-config suggestions for HDD-based OSD node?
Date: Sun, 28 Mar 2010 17:58:21 -0700 [thread overview]
Message-ID: <24075.1269824301@n20.hq.graphstream.com> (raw)
Hello Martin,
martin writes:
>while this does not match your G1, G2 or G3, there is a G4 absolutely
>worth considering IMO:
> Maximize storage area and transfer speed divided by hardware
>investment + MRU.
...
>I think you have to figure out what it is you need done for your
>specific application, and back-track from there. Because there is no
>single optimal configuration of a distributed file system such as Ceph,
>for all applications.
Thanks very much for your comments.
Sorry that I wasn't familiar with your use of the term "MRU" -- please
help me understand.
I agree completely that details of Ceph node and cluster configs that
are most efficient for a specific application, will depend on many
details of that application's requirements.
Craig Dunwoody
cdunwoody@graphstream.com
------------------------------------------------------------------------------
Download Intel® 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
next reply other threads:[~2010-03-29 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 0:58 Craig Dunwoody [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=24075.1269824301@n20.hq.graphstream.com \
--to=cdunwoody@graphstream.com \
--cc=ceph-devel@lists.sourceforge.net \
--cc=martin@millnert.se \
/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.