Some of your overhead is the Wal and rocksdb that are on the OSDs. The Wal is pretty static in size, but rocksdb grows with the amount of objects you have. You also have copies of the osdmap on each osd. There's just overhead that adds up. The biggest is going to be rocksdb with how many objects you have.
On Mon, Feb 12, 2018, 8:06 AM Behnam Loghmani <behnam.loghmani@xxxxxxxxx> wrote:
_______________________________________________Behnam LoghmaniBest regards,what is the best practice for storing small files on bluestore?should I change "bluestore_min_alloc_size_hdd"? and If I change it and set it to smaller size, does it impact on performance?what's the reason of this high disk usage?Actual size of files is something about 32G but it filled 70G of each osd.1 rgw3 mons3 osds (each osd is 100G) - no WAL/DB separation.Hi there,I am using ceph Luminous 12.2.2 with:cluster size 3I stored lots of thumbnails with very small size on ceph with radosgw.
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
