There was a client SSD sorta like that, a bit of Optane with TLC or QLC, but it didn't seem to sell well. Optane was groovy tech, but with certain challenges as well. > On Jan 9, 2024, at 14:30, Mark Nelson <mark.a.nelson@xxxxxxxxx> wrote: > > With HDDs and a lot of metadata, it's tough to get away from it imho. In an alternate universe it would have been really neat if Intel could have worked with the HDD vendors to put like 16GB of user accessible optane on every HDD. Enough for the WAL and L0 (and maybe L1). > > > Mark > > > On 1/9/24 08:53, Anthony D'Atri wrote: >> Not strictly an answer to your worthy question, but IMHO this supports my stance that hybrid OSDs aren't worth the hassle. >> >>> On Jan 9, 2024, at 06:13, Frédéric Nass <frederic.nass@xxxxxxxxxxxxxxxx> wrote: >>> >>> With hybrid setups (RocksDB+WAL on SSDs or NVMes and Data on HDD), if mclock only considers write performance, it may fail to properly schedule read iops (does mclock schedule read iops?) as the calculated iops capacity would be way too high for reads. >> _______________________________________________ >> 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 _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |