It has been proven that the OSDs can’t take advantage of the SSD, so I’ll probably collocate both journal and osd data. Search in the ML for [Single OSD performance on SSD] Can't go over 3, 2K IOPS
You will see that there is no difference it terms of performance between the following: * 1 SSD for journal + 1 SSD for osd data * 1 SSD for both journal and data What you can do in order to max out your SSD is to run multiple journals and osd data on the same SSD. Something like this gave me more IOPS: * /dev/sda1 ceph journal * /dev/sda2 ceph data * /dev/sda3 ceph journal * /dev/sda4 ceph data > On 21 Jan 2015, at 04:32, Andrew Thrift <and...@networklabs.co.nz> wrote: > > Hi All, > > We have a bunch of shiny new hardware we are ready to configure for an all > SSD cluster. > > I am wondering what are other people doing for their journal configuration on > all SSD clusters ? > > - Seperate Journal partition and OSD partition on each SSD > > or > > - Journal on OSD > > > Thanks, > > > > > Andrew > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com Cheers. –––– Sébastien Han Cloud Architect "Always give 100%. Unless you're giving blood." Phone: +33 (0)1 49 70 99 72 Mail: sebastien....@enovance.com Address : 11 bis, rue Roquépine - 75008 Paris Web : www.enovance.com - Twitter : @enovance
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
