cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-174) reduce logging overhead
Date Wed, 29 Jul 2009 15:37:14 GMT

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

Jonathan Ellis commented on CASSANDRA-174:
------------------------------------------

some of the debug() lines don't have the if statement.

rather than optimizing for low line count i think we should optimize for consistency.  otherwise
every time we see a bare debug statement we have to think, "is this off the main path?  or
did someone make a careless mistake?"

> reduce logging overhead
> -----------------------
>
>                 Key: CASSANDRA-174
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-174
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Chris Goffinet
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: 0001-Cleaned-up-logger_.debug-with-isDebugEnabled.patch, 0002-Cleaned-up-logger_.debug-with-isDebugEnabled.patch,
174_3.diff
>
>
> 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