Date: Wed, 31 May 2006 17:11:16 +0200 (CEST) From: Dirk Engling <erdgeist@erdgeist.org> To: "Eugene M. Kim" <freebsd.org@ab.ote.we.lv> Cc: freebsd-hackers@freebsd.org Subject: Re: dump(8) performance Message-ID: <20060531170726.J15476@erdgeist.org> In-Reply-To: <447DB0B1.8040206@ab.ote.we.lv> References: <447DB0B1.8040206@ab.ote.we.lv>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 31 May 2006, Eugene M. Kim wrote: > read throughput was exactly twice as high as the tape write throughput, > throughout the entire dump phases 4 and 5, i.e. dumping actual inodes. > Disappointing, because the tape drive utilization (%busy) was lingering > around 35%-50% for most of the time; I didn't expect the disk would be > the bottleneck. :p I had a similar experience when dumping my mailserver. In addition I noticed that for a user with >300000 files (spam mails) in one directory it caused dump to sit back and think for half an hour before proceeding. I always resolved to look into the code to find something O(x^n) but didn't have the real urge. DID someone here look into that? Regards erdgeist
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060531170726.J15476>