You can set the trace probability on a node to 1% and you'll catch a trace on that table.
http://cassandra.apache.org/doc/latest/tools/nodetool/settraceprobability.html On Mon, Apr 17, 2017 at 11:17 AM, benjamin roth <brs...@gmail.com> wrote: > 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 level and then analyze > the queries. > > Am 17.04.2017 17:07 schrieb "Eren Yilmaz" <eren.yil...@sebit.com.tr>: > >> I can’t add tracing using driver – Usergrid code is way too complex. When >> I look at logging the slow queries on the C* side, it says the feature is >> added in version 3.10 (https://issues.apache.org/jir >> a/browse/CASSANDRA-12403), and we use 3.7. Any other ways to log slow >> queries 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 query log and then trace single queries couldn't >> you? >> >> >> >> Am 17.04.2017 16:31 schrieb "Eren Yilmaz" <eren.yil...@sebit.com.tr>: >> >> I can’t trace selects on the application tables unfortunately. The >> application is Usergrid, and it stores the data in binary. We have little >> control over Usergrid-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 <eren.yil...@sebit.com.tr>: >> >> Application tables use LeveledCompactionStrategy. At first, counter >> tables were created by default SizeTieredCompactionStrategy, but we changed >> them to LeveledCompactionStrategy then. >> >> >> >> compaction = { 'class' : 'org.apache.cassandra.db.compa >> ction.LeveledCompactionStrategy', '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 <eren.yil...@sebit.com.tr>: >> >> 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 reads >> are very slow comparing to the other application data reads from cassandra, >> and sometimes the reads put extra heavy CPU load on some nodes. >> >> >> >> Are there any tips, or best practices for increasing the performance of >> counter tables? >> >> >> >> >> >> >> > -- http://twitter.com/tjake
