apache.org<mailto:user@cassandra.apache.org>
Subject: RE: Counter performance
Just run some queries on counter tables. Some on regular tables. Look at traces
and then compare. You don't need to do anything with application code. You can
also set trace probability on a table leve
017-04-17
> 18:31:49.628000 | cassandra-01 | 5250 | cassandra-01
>
> Processing
> response from / cassandra-05 [SharedPool-Worker-6] | 2017-04-17
> 18:31:49.628000 | cassandra-01 | 5319 | cassandra-01
>
2017-04-17 18:31:49.628595 |
cassandra-01 | 6595 | cassandra-01
From: benjamin roth [mailto:brs...@gmail.com]
Sent: Monday, April 17, 2017 6:17 PM
To: user@cassandra.apache.org
Subject: RE: Counter performance
Just run some queries on counter tables. Some on regular tables. Look at tra
version? Or, what do we expect with this log output?
>>
>>
>>
>> *From:* benjamin roth [mailto:brs...@gmail.com]
>> *Sent:* Monday, April 17, 2017 5:44 PM
>> *To:* user@cassandra.apache.org
>> *Subject:* RE: Counter performance
>>
>>
>>
>&
s in this version? Or, what do we expect with this log output?
>
>
>
> *From:* benjamin roth [mailto:brs...@gmail.com]
> *Sent:* Monday, April 17, 2017 5:44 PM
> *To:* user@cassandra.apache.org
> *Subject:* RE: Counter performance
>
>
>
> You could enable a slow que
? Or, what do we
expect with this log output?
From: benjamin roth [mailto:brs...@gmail.com]
Sent: Monday, April 17, 2017 5:44 PM
To: user@cassandra.apache.org
Subject: RE: Counter performance
You could enable a slow query log and then trace single queries couldn't you?
Am 17.04.2017 16:31 sc
sergrid-created data.
*From:* benjamin roth [mailto:brs...@gmail.com]
*Sent:* Monday, April 17, 2017 4:12 PM
*To:* user@cassandra.apache.org
*Subject:* Re: Counter performance
Do you see difference when tracing the selects?
2017-04-17 13:36 GMT+02:00 Eren Yilmaz :
Applica
Subject: Re: Counter performance
Do you see difference when tracing the selects?
2017-04-17 13:36 GMT+02:00 Eren Yilmaz
mailto:eren.yil...@sebit.com.tr>>:
Application tables use LeveledCompactionStrategy. At first, counter tables were
created by default SizeTieredCompactionStrategy, but we c
tegy then.
>
>
>
> compaction = { 'class' :
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy',
> 'sstable_size_in_mb' : 512 }
>
>
>
> *From:* benjamin roth [mailto:brs...@gmail.com]
> *Sent:* Monday, April 17, 2017 12:12 PM
> *To:* us
'sstable_size_in_mb' : 512 }
From: benjamin roth [mailto:brs...@gmail.com]
Sent: Monday, April 17, 2017 12:12 PM
To: user@cassandra.apache.org
Subject: Re: Counter performance
Do you have a different compaction strategy on the counter tables?
2017-04-17 10:07 GMT+02:00 Eren Yilmaz
m
Do you have a different compaction strategy on the counter tables?
2017-04-17 10:07 GMT+02:00 Eren Yilmaz :
> We are using Cassandra (3.7) counter tables in our application, and there
> are about 10 counter tables. The counter tables are in a separate keyspace
> with RF=3 (total 10 nodes). The ta
We are using Cassandra (3.7) counter tables in our application, and there are
about 10 counter tables. The counter tables are in a separate keyspace with
RF=3 (total 10 nodes). The tables are read-heavy, for each web request to the
application, we read at least 20 counter values. The counter rea
12 matches
Mail list logo
