But then don't I need to evict for every batch of writes? I thought cache would make sense when reads/writes > 1 per say. What do you think?
On Sat, Nov 5, 2016 at 3:33 AM, DuyHai Doan <doanduy...@gmail.com> wrote: > "I have a requirement where I need to know last value that is written > successfully so I could read that value and do some computation and include > it in the subsequent write" > > Maybe keeping the last written value in a distributed cache is cheaper > than doing a read before write in Cassandra ? > > On Sat, Nov 5, 2016 at 11:24 AM, Kant Kodali <k...@peernova.com> wrote: > >> I have a requirement where I need to know last value that is written >> successfully so I could read that value and do some computation and include >> it in the subsequent write. For now we are doing read before write which >> significantly degrades the performance. Light weight transactions are more >> of a compare and set than a Read and Set. The very first thing I tried is >> to see if I can eliminate this need by the application but looks like it is >> a strong requirement for us so I am wondering if there is any way I can >> optimize that? I know batching could help in the sense I can do one read >> for every batch so that the writes in the batch doesn't take a read >> performance hit but I wonder if there is any clever ideas or tricks I can >> do? >> > >
