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 Sat, 27 Jun 2009 01:24:47 GMT

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

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

committed.

this got the "logger_" instances but there are also some with "logger".  Could you get those
too?  And logger_/logger.trace (the level lower than debug).

> reduce logging overhead
> -----------------------
>
>                 Key: CASSANDRA-174
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-174
>             Project: Cassandra
>          Issue Type: Improvement
>            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
>
>
> 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