> -----Original Message----- > From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] On Behalf Of Zoltan Arnold Nagy > Sent: 22 October 2016 15:13 > To: ceph-users <ceph-users@xxxxxxxxxxxxxx> > Subject: cache tiering deprecated in RHCS 2.0 > > Hi, > > The 2.0 release notes for Red Hat Ceph Storage deprecate cache tiering. > > What does this mean for Jewel and especially going forward? > > Can someone shed some light why cache tiering is not meeting the original expectations technically? Hi, Unofficial answer but I suspect it is probably correct. Before Jewel (and later hammer releases), cache tiering reduced performance in pretty much all cases. This was either due to bugs, missing features (proxy write) and/or pre promotion throttling code. To get any use out of it required extremely fine tuning and hand holding. I suspect that the decision to not include it in the RH release was based on prior experience and that a lot of the improvements were implemented towards the end of the release cycle. My guess is a combination of it being too hot and past experience, probably ruled it out. However, I would say that now if you have the right workload (think zipf style) then it actually works reasonably well and would hope that it makes its way back into the enterprise release at some point in the future. Nick > > Thanks, > Zoltan > _______________________________________________ > 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
 |