Re: recommended rocksdb/rockswal sizes when using SSD/HDD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Bruce,

As of right now the WAL should be big enough to hold 4 256MB logs, ie at least 1GB. There's not much point in making it significantly bigger than that, though you certainly can.

The DB size is up to you. The more space you give it, the more likely that you won't end up with metadata rolling over onto the disk. The amount of metadata generated it dependent on many different factors (whether or not CRCs are being stored, the min_alloc size, hwo many extents have been allocated, the number of objects, etc). Generally the more you can give it the better.

Mark

On 08/02/2017 04:26 PM, McFarland, Bruce wrote:
I’m using SDD for the rocksdb/rockswal partitions and putting the data on HDD’s. What is the recommended sizing for these partitions. I’ve read various sizes discussed on the perf call and know that the code defaults of 128MB for rocksdb is small and limits performance. What are the recommended sizes for these partitions?

Thanks,
Bruce

--
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



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux