Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 17 Dec 2013 19:22:09 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12685215.1387306266881.52012.1387308129341@arcas>
In-Reply-To: <JIRA.12685215.1387306266881@arcas>
References: <JIRA.12685215.1387306266881@arcas>
Subject: [jira] [Updated] (HADOOP-10172) Cache SASL server factories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daryn Sharp updated HADOOP-10172:
---------------------------------

    Status: Patch Available  (was: Open)

> Cache SASL server factories
> ---------------------------
>
>                 Key: HADOOP-10172
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10172
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>         Attachments: HADOOP-10172.patch
>
>
> Performance for SASL server creation is _atrocious_.  {{Sasl.createSaslServer}} does not cache the provider resolution for the factories.  Factory resolution and server instantiation has 3 major contention points.  During bursts of connections, one reader accepting a connection stalls other readers accepting connections, in turn stalling all existing connections handled by those readers.
> I benched 5 threads at 187 instances/s - total, not per thread.  With this and another change, I've boosted it to 33K instances/s.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)