You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2013/11/01 23:59:17 UTC

[jira] [Commented] (KAFKA-1115) producer performance affected by trace/debug calls

    [ https://issues.apache.org/jira/browse/KAFKA-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811734#comment-13811734 ] 

Guozhang Wang commented on KAFKA-1115:
--------------------------------------

Hi Francois,

You can change the logging level in config/log4j.properties to avoid printing DEBUG and TRACE level log entries.

> producer performance affected by trace/debug calls
> --------------------------------------------------
>
>                 Key: KAFKA-1115
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1115
>             Project: Kafka
>          Issue Type: Improvement
>          Components: producer 
>    Affects Versions: 0.8
>            Reporter: Francois Saint-Jacques
>            Assignee: Francois Saint-Jacques
>         Attachments: producer-performance-fix.patch
>
>
> After investigating high CPU usage on some producers in production, we found out that a lot of time was passed in string construction for logging of DEBUG and TRACE level.
> This patch removes most of the logging calls, on our systems it cuts CPU usage down to half of what it used to be.
> Note that this is a significant boost in performance for environment where there are thousands of msg/s.



--
This message was sent by Atlassian JIRA
(v6.1#6144)