You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Gunnar Wagenknecht (JIRA)" <ji...@apache.org> on 2013/03/01 17:45:14 UTC

[jira] [Created] (ZOOKEEPER-1657) Wasted CPU cycles be unnecessary SASL checks

Gunnar Wagenknecht created ZOOKEEPER-1657:
---------------------------------------------

             Summary: Wasted CPU cycles be unnecessary SASL checks
                 Key: ZOOKEEPER-1657
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1657
             Project: ZooKeeper
          Issue Type: Bug
          Components: java client
    Affects Versions: 3.4.5
            Reporter: Gunnar Wagenknecht


I did some profiling in one of our Java environments and found an interesting footprint in ZooKeeper. The SASL support seems to trigger a lot times on the client although it's not even in use.

Is there a switch to disable SASL completely?

The attached screenshot shows a 10-minute profiling session on one of our production Jetty servers. The Jetty server handles ~1k web requests per minute. The average response time per web request is a few milli seconds. However, only 32% CPU time are spent in Jetty. In contrast, 65% are spend in ZooKeeper. 

We noticed a significant CPU increase on our servers when deploying an update from ZooKeeper 3.3.2 to ZooKeeper 3.4.5. Thus, we started investigating.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira