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)
We are building a historical timeseries database for stocks and futures,
with trade prices aggregated into daily bars (open, high, low, close values
for the day). The latest bar for each instrument needs to be updated as new
trades arrive on the realtime data feeds. Depending on the trading volume
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
