From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 07:02:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C984816A4D6; Thu, 26 Aug 2004 07:02:25 +0000 (GMT) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38EA243D2F; Thu, 26 Aug 2004 07:02:25 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id C058A50C03; Thu, 26 Aug 2004 16:02:23 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black.imgsrc.co.jp (Postfix) with ESMTP id 74AAD50C01; Thu, 26 Aug 2004 16:02:21 +0900 (JST) Date: Thu, 26 Aug 2004 16:02:21 +0900 Message-ID: <7mllg25qma.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Tim Kientzle In-Reply-To: <412D8958.7050707@freebsd.org> References: <7m3c2e88xk.wl@black.imgsrc.co.jp> <412D6534.9030503@freebsd.org> <412D68AD.7050906@freebsd.org> <7moeky5wyg.wl@black.imgsrc.co.jp> <412D8958.7050707@freebsd.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 cc: Jun Kuriyama cc: Current Subject: Re: bsdtar eats CPU when extracting POSIX tar archive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 07:02:25 -0000 At Wed, 25 Aug 2004 23:55:20 -0700, Tim Kientzle wrote: > Looks like it could be network related. I see almost > 5,000 calls to recvfrom. With that much network I/O, > any network issues on that box would definitely cause problems. > > Do you know what's causing that? Is it uid/gid lookups, > perhaps? bsdtar does not (yet) do any caching of uid/gid > lookups; once I implement that, it will definitely have a > big performance impact for folks using NIS or LDAP. But > that still seems like a lot. I wonder if there's something > else going on? Hmm, yes, this box uses NIS as client. I confirmed a lot of NIS packets during extraction. Is GNU tar implemented such a caching? Using gtar is faster like usual on my box. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project