Date: Mon, 29 Nov 2004 23:27:47 -0600 From: "Conrad J. Sabatier" <conrads@cox.net> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade and index Message-ID: <20041129232747.528fdce4@dolphin.local.net> In-Reply-To: <20041130035734.GA36416@xor.obsecurity.org> References: <000501c4d68f$74a82320$0400a8c0@satellite> <20041130035734.GA36416@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Nov 2004 19:57:34 -0800, Kris Kennaway <kris@obsecurity.org> wrote: > On Mon, Nov 29, 2004 at 10:48:29PM -0500, dave wrote: > > Hello, > > I've got a box that runs portupgrade to keep the most current > > ports. > > I've lately switched to make fetchindex vs. portsdb -uU which goes > > much faster. My problem is whenever i do a make search for a port > > the index.5 file is regenerated and that takes an extremely long > > time. I was wondering if this is normal behavior, and what if > > anything i could do to speed it up? > > make fetchindex > > Kris You can also increase the concurrency of "portsdb -U"/"make index" by setting INDEX_JOBS in /etc/make.conf. The default number of parallel jobs is 2. Increasing this to, say, 8, will save some time in building the index. You can save yourself a lot of headaches if you do a nightly cvsup via cron and rebuild the index at that time. -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129232747.528fdce4>