[
https://issues.apache.org/jira/browse/HADOOP-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761124#comment-16761124
]
Wei-Chiu Chuang commented on HADOOP-16059:
------------------------------------------
Thanks for clarification, [~ayushtkn]
I understand the idea of caching, and from a quick peek the patch looks
reasonable. It is especially useful for SASL server since it gets lots of
client connections.
On the other hand, clients are usually long lived connections and you typically
don't connect to more a handful of name services at a time, so I suspected the
overhead of setting up the SASL client isn't so noticeable. "premature
optimization is the root of all evils" as it is claimed, so wanted to know how
much overhead does this patch eliminates, if there's a profiling already done.
> Use SASL Factories Cache to Improve Performance
> -----------------------------------------------
>
> Key: HADOOP-16059
> URL: https://issues.apache.org/jira/browse/HADOOP-16059
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Critical
> Attachments: HADOOP-16059-01.patch, HADOOP-16059-02.patch,
> HADOOP-16059-02.patch, HADOOP-16059-03.patch, HADOOP-16059-04.patch
>
>
> SASL Client factories can be cached and SASL Server Factories and SASL Client
> Factories can be together extended at SaslParticipant to improve performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
