Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 94842 invoked from network); 19 Mar 2010 19:24:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Mar 2010 19:24:48 -0000 Received: (qmail 8304 invoked by uid 500); 19 Mar 2010 19:24:48 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 8261 invoked by uid 500); 19 Mar 2010 19:24:48 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 8230 invoked by uid 99); 19 Mar 2010 19:24:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Mar 2010 19:24:48 +0000 X-ASF-Spam-Status: No, hits=-1072.3 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Mar 2010 19:24:47 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 42723234C4B1 for ; Fri, 19 Mar 2010 19:24:27 +0000 (UTC) Message-ID: <734223743.371621269026667271.JavaMail.jira@brutus.apache.org> Date: Fri, 19 Mar 2010 19:24:27 +0000 (UTC) From: "Konstantin Shvachko (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-6637) Benchmark overhead of RPC session establishment In-Reply-To: <2126592612.323051268859087170.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847526#action_12847526 ] Konstantin Shvachko commented on HADOOP-6637: --------------------------------------------- I ran the benchmark on three versions of hadoop # 0.20.1, which does not have any security code, and therefore kerberos and delegation token authentications are not applicable there. # 0.20.100, which contains the latest state of security implementation # 0.22.trunk, which does not have all the latest security patches applied at the time of benchmarking (just for the reference) The benchmark creates a connection to the RPC server 1000 times. Each time the RPC server authenticates the client using one of the three authentication methods (no authentication, kerberos, delegation token). The result if the average latency of the connection request. The table below shows that - when security is turned off the the new code still adds 14% overhead. - The overhead for kerberos authentication is predictably huge. - The delegation token authentication was intended as a fast alternative to kerberos. It is somewhat faster, but not as nearly as the non-secure version. This should definitely be the focus of future optimizations. - 0.22 is 1-2% slower compared to 0.20.100. It is expected to catch up with it, when all latest security contributions are ported to the trunk. ||Version||No security||Kerberos||Delegation Tooken|| |0.20.1 |0.920| | | |0.20.100|1.047 (+14%)|44.670|42.615| |0.22 |1.597 (+73%)|45.148|43.455| > Benchmark overhead of RPC session establishment > ------------------------------------------------ > > Key: HADOOP-6637 > URL: https://issues.apache.org/jira/browse/HADOOP-6637 > Project: Hadoop Common > Issue Type: Test > Components: benchmarks > Affects Versions: 0.20.2 > Reporter: Konstantin Shvachko > Assignee: Konstantin Shvachko > Fix For: 0.20.3 > > Attachments: miniRPCBenchmark-20.patch, miniRPCBenchmark.patch, miniRPCBenchmark.patch > > > Measure the latency of RPC session establishments through three mechanisms: > # simple - no auth > # kerberos authentication > # delegation token authentication -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.