The write performance of INSERT or UPDATE is very high in C*, but if you update too often the row you update frequently will be in many SSTables so the read latency and system load will be increased until these SSTables are compacted into one single file.
I think you can use redis (or memcache) to cache the read request. Write into C* and redis both and read only from redis for the latest bar. Read from C* for previous bars if the memory size is bottleneck. Thanks, Philo Yang 2014-08-14 2:13 GMT+08:00 Robert Coli <rc...@eventbrite.com>: > On Wed, Aug 13, 2014 at 8:01 AM, Jeremy Jongsma <jer...@barchart.com> > wrote: > >> I've read comments about frequent column updates causing compaction >> issues with Cassandra. What is the recommended Cassandra configuration / >> best practices for usage scenarios like this? >> > > If your data is frequently UPDATEd, perhaps a log structured database with > immutable data files is not for you? > > =Rob > >
