From owner-freebsd-performance@FreeBSD.ORG Wed Mar 9 04:15:52 2005 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF8116A4CE for ; Wed, 9 Mar 2005 04:15:52 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D057E43D1D for ; Wed, 9 Mar 2005 04:15:51 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so73199rnf for ; Tue, 08 Mar 2005 20:15:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=GoXCZAl8jhFaFiYTwy9qbpLhPYkjrDpgMRj3X6GPXOSdkMKdN2ZeTNY9I9NJBDOKahEajJuNMWrnTX0lfHMESKsrJ2UJ/TYVa56qdSv9/N0XHjgebOaEG4GGI72gavUm4BKziwdPwQtDyr6dpDTs24/04tXCPXkAVKFvUW/a2Gw= Received: by 10.38.181.32 with SMTP id d32mr441137rnf; Tue, 08 Mar 2005 20:15:51 -0800 (PST) Received: by 10.38.209.22 with HTTP; Tue, 8 Mar 2005 20:15:51 -0800 (PST) Message-ID: <84dead720503082015c11bb53@mail.gmail.com> Date: Wed, 9 Mar 2005 04:15:51 +0000 From: Joseph Koshy To: Peter Hessler In-Reply-To: <20050309015119.44566908B7@coverity.dreamhost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050309005628.5C6D1908B8@coverity.dreamhost.com> <422E541C.8040108@telus.net> <20050309014632.49895908B7@coverity.dreamhost.com> <20050309015119.44566908B7@coverity.dreamhost.com> cc: freebsd-performance@freebsd.org Subject: Re: NFS small files X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 04:15:52 -0000 > I should mention that copying the same directory on the nfs server takes Filename resolution over NFS involves multiple round-trip requests, one for each component of the file's pathname. For example, assuming that '/mnt' is an NFS mount-point, accessing a file named '/mnt/FreeBSD/src/sys/sys/file.h,v' results in the following NFS requests: [Edited output from ethereal] 1 0.000000 ::1 ::1 NFS V3 LOOKUP Call (Reply In 2), DH:0xa9a212b8/FreeBSD V3 Procedure: LOOKUP (3) what: dir Name: FreeBSD 2 0.000116 ::1 ::1 NFS V3 LOOKUP Reply (Call In 1), FH:0xcd6610c4 Status: OK (0) 3 0.000162 ::1 ::1 NFS V3 LOOKUP Call (Reply In 4), DH:0xcd6610c4/src V3 Procedure: LOOKUP (3) what: dir Name: src 4 0.000194 ::1 ::1 NFS V3 LOOKUP Reply (Call In 3), FH:0x5c9e0ec6 Status: OK (0) 5 0.000224 ::1 ::1 NFS V3 LOOKUP Call (Reply In 6), DH:0x5c9e0ec6/sys V3 Procedure: LOOKUP (3) what: dir Name: sys 6 0.000253 ::1 ::1 NFS V3 LOOKUP Reply (Call In 5), FH:0xb4d2113a Status: OK (0) 7 0.000281 ::1 ::1 NFS V3 LOOKUP Call (Reply In 8), DH:0xb4d2113a/sys V3 Procedure: LOOKUP (3) what: dir Name: sys 8 0.000312 ::1 ::1 NFS V3 LOOKUP Reply (Call In 7), FH:0xb0f9f738 Status: OK (0) 9 0.000338 ::1 ::1 NFS V3 LOOKUP Call (Reply In 10), DH:0xb0f9f738/file.h,v V3 Procedure: LOOKUP (3) what: dir Name: file.h,v 10 0.000366 ::1 ::1 NFS V3 LOOKUP Reply (Call In 9), FH:0x58ea0f3a Status: OK (0) 11 0.002220 ::1 ::1 NFS V3 ACCESS Call, FH:0xa9a212b8 V3 Procedure: ACCESS (4) object access: 0x3f I can imagine that the extra latency induced by these round-trips would be adding to elapsed time for your test. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy