|
Hey all! I have a ceph with multiple HDD and 1 really fast SSD with (30GB per OSD) per host. I have been thinking and all docs say that I should give all the SSD space for RocksDB, so I would have a HDD data and a 30GB partition for RocksDB. But it came to my mind that if the OSD isnt full maybe I am not using all the space in the SSD, or maybe I prefer having a really small amount of hot k/v and metadata and the data itself in a really fast device than just storing all could metadata. So I though that using Bcache to make SSD to be a cache and as metadata and k/v are usually hot, they should be place on the cache. But this doesnt guarantee me that k/v and metadata are actually always in the SSD cause under heavy cache loads it can be pushed out (like really big data files). So I came up with the idea of setting small 5-10GB partitions for the hot RocksDB and the rest to use it as a cache, so I make sure that really hot metadata is actually always on the SSD and the coulder one should be also on the SSD (as a bcache) if its not really freezing, in that case they would be pushed to the HDD. It also doesnt make anysense to have metadatada that you never used using space on the SSD, I rather use that space to store hotter data. This is also make writes faster, and in blueStore we dont have the double write problem so it should work fine. What do you think about this? does it have any downsite? is there any other way? Jorge Pinilla López jorpilo@xxxxxxxxx Estudiante de ingenieria informática Becario del area de sistemas (SICUZ) Universidad de Zaragoza PGP-KeyID: A34331932EBC715A |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
