From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: ceph, slow (cheap) and fast (expensive) storage?
Date: Tue, 8 Jun 2010 12:41:21 +0000 (UTC) [thread overview]
Message-ID: <huldph$fmu$1@dough.gmane.org> (raw)
In-Reply-To: 4C0E1BAC.8070306@wpkg.org
Am Tue, 08 Jun 2010 12:30:04 +0200 schrieb Tomasz Chmielewski:
> I'd like to build a cluster for storing large amounts of data.
>
> The cluster would consist of slow (cheap) storage and fast (expensive)
> storage.
>
> I would like to migrate data from fast (expensive) storage to slow
> (cheap) storage if it wasn't accessed for, say, 6 months.
>
> Would ceph somehow help me achieve that?
I would not expect to be the fast (expensive) storage to be that faster
in a ceph cluster. if you get enough cheap storage nodes it will scale
with the amount of disks/nics as the date is striped among all the nodes
(osd's). But this is just my speculation.
if you have some amount storage nodes and you are on GigE you will hit
the ethernet limit on the client faster than anything else.
"cheap" not in sens of crap hardware. cheap as in SATA 24x7 enterprise
drives.
and remember:
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
- Thomas
PS: "cheap" storage selfmade:
http://blog.backblaze.com/2009/09/01/petabytes-on-a-budget-how-to-build-
cheap-cloud-storage/
next prev parent reply other threads:[~2010-06-08 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 10:30 ceph, slow (cheap) and fast (expensive) storage? Tomasz Chmielewski
2010-06-08 10:53 ` Wido den Hollander
2010-06-08 12:04 ` Tomasz Chmielewski
2010-06-08 13:13 ` ales-76
2010-06-08 12:41 ` Thomas Mueller [this message]
2010-06-08 18:03 ` Sage Weil
2010-06-08 17:51 ` Sage Weil
2010-06-09 14:55 ` Tomasz Chmielewski
2010-06-09 15:11 ` Wido den Hollander
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='huldph$fmu$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@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 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.