If I correctly understand the discussion, you are correct
that I/O could be saved by doing this ... were it not for
the fact the I/O in question is already being saved much
more effectively by someone else.
The entire web is richly festooned with cache servers whose
sole raison d'etre is to solve precisely this problem. They
are so good at it that back-bone providers often find it more
cash-efficient to buy more cache servers than to lay more
fiber. Cache servers don't merely save disk I/O, they catch
these requests before they reach the server (or even the
backbone).
On 04/15/2013 01:06 PM, Gandalf Corvotempesta wrote:
Currently reads always come from the primary OSD in the placement group
rather than a secondary even if the secondary is closer to the client.
In this way, only one OSD will be involved in reading an object, this
will
result in a bottleneck if multiple clients needs to access to the same
file.
For example, a 3KB CSS file served by a webserver to 400 users, will be
read just from one OSD. 400 users directed to 1 OSD while (in case of
replica 3) other 2 OSDs are available?
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
