From owner-freebsd-ports@FreeBSD.ORG Fri Nov 24 07:08:54 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67C3616A4A0 for ; Fri, 24 Nov 2006 07:08:54 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A6EB43D46 for ; Fri, 24 Nov 2006 07:08:14 +0000 (GMT) (envelope-from vehemens@verizon.net) Received: from susy.dsl-verizon.net ([71.106.233.100]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0J9800KTD3UP41S4@vms040.mailsrvcs.net> for freebsd-ports@freebsd.org; Fri, 24 Nov 2006 01:08:49 -0600 (CST) Date: Thu, 23 Nov 2006 23:02:43 -0800 From: vehemens To: freebsd-ports@freebsd.org Message-id: <200611232302.44025.vehemens@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline User-Agent: KMail/1.9.4 Subject: Re: pkgdb 2.2.2 is abysmally slow X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2006 07:08:54 -0000 On Thu, Nov 23, 2006 at 21:36:53, Joe Marcus Clarke wrote: > The pkgdb that ships with portupgrade-2.2.2 is orders of magnitude > slower that that of 2.1.3.3. On a machine with 472 ports, if I upgrade > nspr the time to run pkgdb -fF after the upgrade is about ten minutes. > Prior to upgrading to portupgrade-2.2.2, the same operation took about > three seconds. The result is portupgrades slow down to a crawl since > pkgdb needs to be run between the build completion and the > uninstall/upgrade portion. It's really bad with 700+ ports (i.e. xorg modular, gnome ports, and a few others sprinked in). Anybody know what the processing time is for "portupgrade -arRW" as a function of the number of ports before and after the last update?