Range query is not that important in nowadays SSD----you can see very high read random read IOPS in ssd spec, and getting higher day by day.The key problem
here is trying to exactly matching one query(get/put) to one SSD IO(read/write), eliminate the read/write amplification. We kind of believe OpenNvmKV may be the right approach. Back to the context of Ceph, can we find some use case of nowadays key-value backend? We would like to learn from community what’s the workload pattern if
you wants a K-V backed Ceph? Or just have a try? I think before we get a suitable DB backend ,we had better off to optimize the key-value backend code to support specified kind of load. From: Haomai Wang [mailto:haomaiwang@xxxxxxxxx]
Exactly, I'm just looking forward a better DB backend suitable for KeyValueStore. It maybe traditional B-tree design. Kinetic original I think it was a good backend, but it doesn't support range query :-( On Mon, Dec 1, 2014 at 10:04 PM, Chen, Xiaoxi <xiaoxi.chen@xxxxxxxxx> wrote:
-- Best Regards, Wheat |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com