Hi, I'm pretty sure that it's related to this ticket : https://issues.apache.org/jira/browse/CASSANDRA-5677
I'd be happy if someone tests this patch. It should apply easily on 1.2.5 & 1.2.6 After applying the patch, by default, the current implementation is still used, but modify your cassandra.yaml to add the following one : interval_tree_provider: IntervalTreeAvlProvider (Note that implementations should be interchangeable, because they share the same serializers and deserializers) Also, please note that this patch has not been reviewed nor intensively tested... So, it may not be "production ready" Fabien 2013/6/26 Theo Hultberg <t...@iconara.net> > Hi, > > I've seen a couple of people on Stack Overflow having problems with > performance when they have maps that they continuously update, and in > hindsight I think I might have run into the same problem myself (but I > didn't suspect it as the reason and designed differently and by accident > didn't use maps anymore). > > Is there any reason that maps (or lists or sets) in particular would > become a performance issue when they're heavily modified? As I've > understood them they're not special, and shouldn't be any different > performance wise than overwriting regular columns. Is there something > different going on that I'm missing? > > Here are the Stack Overflow questions: > > > http://stackoverflow.com/questions/17282837/cassandra-insert-perfomance-issue-into-a-table-with-a-map-type/17290981 > > > http://stackoverflow.com/questions/17082963/bad-performance-when-writing-log-data-to-cassandra-with-timeuuid-as-a-column-nam/17123236 > > yours, > Theo > -- Fabien Rousseau * * <aur...@yakaz.com>www.yakaz.com
