You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/07/29 08:38:14 UTC

[jira] Updated: (CASSANDRA-174) reduce logging overhead

     [ https://issues.apache.org/jira/browse/CASSANDRA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Greene updated CASSANDRA-174:
-------------------------------------

    Attachment: 174_3.diff

This should finally finish this off.  Indiscriminate application of conditional on debug logging -- but there were some good ones still in the read/write path that this catches.

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