UPDATING 20110730

[Doug Barton]

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/