Date: Thu, 26 Aug 2004 16:02:21 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Tim Kientzle <kientzle@freebsd.org> Cc: Current <freebsd-current@freebsd.org> Subject: Re: bsdtar eats CPU when extracting POSIX tar archive Message-ID: <7mllg25qma.wl@black.imgsrc.co.jp> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mllg25qma.wl>