From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 3 04:20:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA00B16A420 for ; Sat, 3 Jun 2006 04:20:58 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 429DA43D46 for ; Sat, 3 Jun 2006 04:20:57 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k534KkAe001740; Fri, 2 Jun 2006 23:20:46 -0500 (CDT) (envelope-from dan) Date: Fri, 2 Jun 2006 23:20:46 -0500 From: Dan Nelson To: Zaphod Beeblebrox Message-ID: <20060603042046.GA19262@dan.emsphone.com> References: <447DB0B1.8040206@ab.ote.we.lv> <20060531153029.GE6982@dan.emsphone.com> <447DBA44.1060605@ab.ote.we.lv> <5f67a8c40605310953h27bf170oa474200cd4b93c03@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f67a8c40605310953h27bf170oa474200cd4b93c03@mail.gmail.com> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: "Eugene M. Kim" , freebsd-hackers@freebsd.org Subject: Re: dump(8) performance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jun 2006 04:20:59 -0000 In the last episode (May 31), Zaphod Beeblebrox said: > On 5/31/06, Eugene M. Kim wrote: > >Dan Nelson wrote: > >> Are you using the -C option to dump? I would expact that to help > >> more in the "dumping directories" step, but it might help later > >> phases too. > > > >Yep, -C32. > > I'm a pretty big fan of using team (ports/misc/team). Team > implements a ring buffer for the output of dump. Is the -C argument > an output buffer or a buffer at some other level of the process? It's a read cache. -- Dan Nelson dnelson@allantgroup.com