On 11/12/13 19:09, Sage Weil wrote:
That is one part. The current strategy of layering on top of a file system and using a write-ahead journal makes sense given the existing linux fs building blocks, but is far from an optimal solution for many workloads. A k/v interface based on something leveldb probably performs much better for many small-object use-cases. Also, a k/v backend can take advatange of emerging non-block storage interfaces like NVMKV, Kinetic, new libraries like rocksdb, etc.
Yeah, the pluggable backend approach seems like a really good plan. Regards Mark -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
