2013/4/16 Mark Kampe <mark.kampe@xxxxxxxxxxx>: > 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). Mine was just an example, there are many other cases where a frotnend cache is not possible. I think that ceph should spread reads across the whole clusters by default (like a big RAID-1), to archieve bandwidth improvement. Glusters does this, and also MooseFS. What happens in case of a big file (for example, 100MB) with multiple chunks? Is ceph smart enough to read multiple chunks from multiple servers simultaneously or the whole file will be served by just an OSD ? -- 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
