cassandra-commits mailing list archives

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

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

Chris Goffinet commented on CASSANDRA-174:
------------------------------------------

Yes. Might be easier for me to just resolve conflicts after your stuff is ready. Since a lot
of the work was just formatting the statements nicely. The script is pretty simple.

> 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
>
>
> 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