Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1639227462.1246065887185.JavaMail.jira@brutus>
Date: Fri, 26 Jun 2009 18:24:47 -0700 (PDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-174) reduce logging overhead
In-Reply-To: <541275802.1242272205670.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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