UPDATING 20110730

[Andriy Gapon]

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