From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 06:55:29 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 9EC5816A4CF for ; Thu, 26 Aug 2004 06:55:29 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B2F743D58 for ; Thu, 26 Aug 2004 06:55:29 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i7Q6tL90027957; Wed, 25 Aug 2004 23:55:29 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <412D8958.7050707@freebsd.org> Date: Wed, 25 Aug 2004 23:55:20 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jun Kuriyama References: <7m3c2e88xk.wl@black.imgsrc.co.jp> <412D6534.9030503@freebsd.org> <412D68AD.7050906@freebsd.org> <7moeky5wyg.wl@black.imgsrc.co.jp> In-Reply-To: <7moeky5wyg.wl@black.imgsrc.co.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 06:55:29 -0000 Jun Kuriyama wrote: > Tim Kientzle wrote: > >>I'm suspicious that all of the time being used is >>system time. > > Thank you for your investigation. This problem is happened on my dual > P-III box, but I cannot reproduce it on another P4 box. I'll try what > is different on them. > > http://www.imgsrc.co.jp/~kuriyama/tmp/20040826-tar-kdump.log.gz > > Looks kqueue related? 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? Tim