From: Nathan Cutler <ncutler@suse.cz>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: which osds get used for ec pool reads?
Date: Thu, 14 May 2015 21:07:56 +0200 [thread overview]
Message-ID: <5554F28C.8040706@suse.cz> (raw)
In-Reply-To: <CAC6JEv_xsOVPh2RxRgGD=K2Q0bj_u13TmgkAhP1Jn5CEWMJLgw@mail.gmail.com>
On 05/14/2015 08:33 PM, Gregory Farnum wrote:
> If you read every block, you increase the amount of data accessed but
> can avoid the long tail latencies. There are a bunch of research
> papers about these tradeoffs and the surprising latency improvements
> you can get on the aggregate read, and Yahoo! talked about this in
> their blog post on their use of Ceph. :)
Here's the link, might save some googling:
http://yahooeng.tumblr.com/post/116391291701/yahoo-cloud-object-store-object-storage-at
next prev parent reply other threads:[~2015-05-14 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 16:27 which osds get used for ec pool reads? Deneau, Tom
2015-05-14 16:52 ` Samuel Just
2015-05-14 18:23 ` Somnath Roy
2015-05-14 18:33 ` Gregory Farnum
2015-05-14 19:07 ` Nathan Cutler [this message]
2015-05-14 19:54 ` Somnath Roy
2015-05-14 19:56 ` Sage Weil
2015-05-14 20:20 ` Samuel Just
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=5554F28C.8040706@suse.cz \
--to=ncutler@suse.cz \
--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.