In addition to what the others said - generally there is little point in splitting block and wal partitions - just stick to one for both. What model are you SSDs and how well do they handle small direct writes? Because that's what you'll be getting on them and the wrong type of SSD can make things worse rather than better. On Tue, 9 Nov 2021 at 00:08, Boris Behrens <bb@xxxxxxxxx> wrote: > > Hi, > we run a larger octopus s3 cluster with only rotating disks. > 1.3 PiB with 177 OSDs, some with a SSD block.db and some without. > > We have a ton of spare 2TB disks and we just wondered if we can bring the > to good use. > For every 10 spinning disks we could add one 2TB SSD and we would create > two partitions per OSD (130GB for block.db and 20GB for block.wal). This > would leave some empty space on the SSD for waer leveling. > > The question now is: would we benefit from this? Most of the data that is > written to the cluster is very large (50GB and above). This would take a > lot of work into restructuring the cluster and also two other clusters. > > And does it make a different to have only a block.db partition or a > block.db and a block.wal partition? > > Cheers > Boris > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |