From owner-freebsd-ports@FreeBSD.ORG Tue Aug 2 19:12:51 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9604A106564A; Tue, 2 Aug 2011 19:12:51 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B3E468FC16; Tue, 2 Aug 2011 19:12:50 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA26117; Tue, 02 Aug 2011 22:12:49 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QoKOX-000Hx1-1U; Tue, 02 Aug 2011 22:12:49 +0300 Message-ID: <4E384C30.50105@FreeBSD.org> Date: Tue, 02 Aug 2011 22:12:48 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Doug Barton 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> In-Reply-To: <4E384155.1080507@FreeBSD.org> X-Enigmail-Version: 1.2pre 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 19:12:51 -0000 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. Typically performance-conscious applications explicitly pull such data into an application cache. But practice is the main criterion. -- Andriy Gapon