From owner-freebsd-ports@FreeBSD.ORG Tue Aug 2 20:08:36 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id E33C31065672; Tue, 2 Aug 2011 20:08:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-4.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id DAA8014FEDD; Tue, 2 Aug 2011 20:08:35 +0000 (UTC) Message-ID: <4E385943.1060703@FreeBSD.org> Date: Tue, 02 Aug 2011 13:08:35 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110723 Thunderbird/5.0 MIME-Version: 1.0 To: Andriy Gapon References: <4E345DBD.1090503@FreeBSD.org> <4E34B0BB.9050008@FreeBSD.org> <4E353A46.1050204@FreeBSD.org> <4E35A998.5060102@FreeBSD.org> <4E37F81F.7040902@FreeBSD.org> <4E384155.1080507@FreeBSD.org> <4E384C30.50105@FreeBSD.org> In-Reply-To: <4E384C30.50105@FreeBSD.org> X-Enigmail-Version: 1.2pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: UPDATING 20110730 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: Tue, 02 Aug 2011 20:08:37 -0000 On 08/02/2011 12:12, Andriy Gapon wrote: > on 02/08/2011 21:26 Doug Barton said the following: >> On 08/02/2011 06:14, Andriy Gapon wrote: >>> Second, I think that portmaster could cache the origin => pkg mapping that it >>> builds while working on port A, so that it can be readily re-used for port B. >>> That could also include "negative" mapping where there is no installed pkg for a >>> given origin. >> >> That's a reasonable idea, but moderately complex to do. I'll put it on >> "the list" but it's not going to be a priority since in non-worst-case >> scenarios it's generally quite fast as it is. >> >> Meanwhile thanks for digging further into your situation and confirming >> that it's a local problem. > > Well, yes with a little bit of no. > I will repeat myself: currently portmaster's performance relies on the fact that > certain often used data originating from disk is actually cached in memory by > the OS. And I will repeat myself, one last time. The assumptions that portmaster makes are reasonable under typical conditions, but can be improved which I will do in due course. However, your conditions are very non-typical, including but not limited to: slow disk, small amount of ram, zfs on a slow disk with a small amount of ram, poorly tuned zfs on a slow disk with a small amount of ram, and a large'ish number of ports installed. I get that you're disappointed with portmaster's performance under these circumstances, and I've already said that I will do what I can, when I can, to improve that. Hopefully I won't need to repeat myself again. :) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/