public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ceph on btrfs
Date: Thu, 23 Oct 2014 19:41:22 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141023T200237-774@post.gmane.org> (raw)
In-Reply-To: 20141023174903.dfc6e5be9f0213c4cd884101@gmail.com

Andrew Savchenko <bircoph <at> gmail.com> writes:


> Ceph is optimized for btrfs by design, it has no configure options
> to enable or disable btrfs-related stuff:
> https://github.com/ceph/ceph/blob/master/configure.ac
> No configure option => no use flag.

Good to know; nice script.

> Just use the latest (0.80.7 ATM). You may just nerame and rehash
> 0.80.5 ebuild (usually this works fine). Or you may stay with
> 0.80.5, but with fewer bug fixes.

So just download from ceph.com, put it in distfiles and copy-edit
ceph-0.80.7 in my /usr/local/portage,  or is there an overlay somewhere
I missed?

> If raid is supposed to be read more frequently than written to,
> then my favourite solution is raid-10-f2 (2 far copies, perfectly
> fine for 2 disks). This will give you read performance of raid-0 and
> robustness of raid-1. Though write i/o will be somewhat slower due
> to more seeks. Also it depends on workload: if you'll have a lot of  
> independent read requests, raid-1 will be fine too. But for large read  
> i/o from a single or few clients raid-10-f2 is the best imo.

Interesting. For now I'm going to stay with simple mirroring. After
some time I might migrate to a more agressive FS arrangement, once
I have a better idea of the i/o needs. With spark(RDD)  on top of mesos,
I shooting for mostly "in-memory" usage so i/o  is not very heavily
used. We'll just have to see how things work out.

Last point. I'm using openrc and not systemd, at this time; any
ceph issues with openrc, as I do see systemd related items with ceph.


> Andrew Savchenko


Very good advice.
Thanks,
James





  reply	other threads:[~2014-10-23 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 20:05 [gentoo-user] ceph on btrfs James
2014-10-23 13:49 ` Andrew Savchenko
2014-10-23 19:41   ` James [this message]
2014-10-24 10:02     ` [gentoo-user] " Andrew Savchenko
2014-10-24 16:20       ` James
2014-10-25 10:00         ` Andrew Savchenko

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=loom.20141023T200237-774@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox