> On Dec 14, 2023, at 10:32 AM, Ariel Weisberg <ar...@weisberg.ws> wrote: > > 1. Fork OHC and start publishing under a new package name and continue to use > it
Who would fork it? Where would you fork it? My first instinct is that this would not be viable path forward. > 2. Replace OHC with a different cache implementation like Caffeine which > would move it on heap Doesn’t seem optimal but given the advent of newer garbage collectors, we might be able to run Cassandra with larger heap sizes and moving this to heap may be a non-issue. Someone needs to try it out and measure the performance impact with Zgc or Shenandoah. > 3. Deprecate the row cache entirely in either 5.0 or 5.1 and remove it in a > later release In my experience, Row cache has historically helped in narrow workloads where you have really hot rows but in other workloads it can hurt performance. So keeping it around may be fine as long as people can disable it. Moving it on-heap using Caffeine maybe the easiest option here. Dinesh
