cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-174) reduce logging overhead
Date Tue, 16 Jun 2009 17:47:07 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720258#action_12720258
] 

Sandeep Tata commented on CASSANDRA-174:
----------------------------------------

Yes, using the if(logger.isDebugEnabled()) check seems like the best option.

> reduce logging overhead
> -----------------------
>
>                 Key: CASSANDRA-174
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-174
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Priority: Critical
>             Fix For: 0.4
>
>
> Logging overhead dominates workload for small column values.  This can be mitigated by
switching to INFO but you still have the overhead of throwing all those strings together.
 Some ideas here: http://surguy.net/articles/removing-log-messages.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message