cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Joyce (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7022) Consider an option to reduce tracing cost by writing only to sessions table (not events)
Date Thu, 10 Apr 2014 15:22:15 GMT
Bill Joyce created CASSANDRA-7022:
-------------------------------------

             Summary: Consider an option to reduce tracing cost by writing only to sessions
table (not events)
                 Key: CASSANDRA-7022
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7022
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
         Environment: C* 2.0.6 running on Ubuntu 12.04
            Reporter: Bill Joyce
            Priority: Minor


With MySQL and SQL Server, I can profile all queries in high traffic production environments.
I'm assuming the bulk of the C* tracing cost comes in writing to the system_traces.events
table, so it would be great to have an option to write just the system_traces.session info
if that allows me to run 'nodetool settraceprobability' with a higher probability (ideally
a probability of 1). This along with CASSANDRA-7021 would go a long way in giving us performance
analysis closer to what can be done with more mature back ends.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message