Cassandra query degradation with high frequency updated tables.

2015-10-08 Thread Nazario Parsacala
Hi, so we are developing a system that computes profile of things that it observes. The observation comes in form of events. Each thing that it observe has an id and each thing has a set of subthings in it which has measurement of some kind. Roughly there are about 500 subthings within each th

Re: Cassandra query degradation with high frequency updated tables.

2015-10-09 Thread Nazario Parsacala
e.org/jira/browse/CASSANDRA-10270>, > which was fixed in 2.2.2. > > Additionally, you may want to look into using leveled compaction > (http://www.datastax.com/dev/blog/when-to-use-leveled-compaction > <http://www.datastax.com/dev/blog/when-to-use-leveled-compaction>).

Re: Cassandra query degradation with high frequency updated tables.

2015-10-09 Thread Nazario Parsacala
Compaction did not help too. > On Oct 9, 2015, at 1:01 PM, Nazario Parsacala wrote: > > So I upgraded to 2.2.2 and change the compaction strategy from > DateTieredCompactionStrategy to LeveledCompactionStrategy. But the problem > still exists. > At the start we were

Re: Cassandra query degradation with high frequency updated tables.

2015-10-09 Thread Nazario Parsacala
Read 468 live and 0 tombstone cells [SharedPool-Worker-2] | 2015-10-09 16:44:11.329000 | 172.31.17.129 | 987011

Re: Cassandra query degradation with high frequency updated tables.

2015-10-09 Thread Nazario Parsacala
RA > <https://issues.apache.org/jira/browse/CASSANDRA>) with your schema, details > on your data layout, and these traces? > > On Fri, Oct 9, 2015 at 3:47 PM, Nazario Parsacala <mailto:dodongj...@gmail.com>> wrote: > > > So the trace is varying a lot. And does not

Subscribe

2010-05-26 Thread Nazario Parsacala
Sent from my iPhone

Read latency on one ColumnFamily greater than the rest of Column Families ..

2010-06-11 Thread Nazario Parsacala
So I have setup some test with Cassandra (with OCM). Though not very impressed with the single read speeds , I have observed that it does scale very well even with numerous number of concurrent readers .. However I have observed that no matter what I do , I am somehow limitted to around 4 ms of rea