[gentoo-portage-dev] slow dependency checking

[gentoo-portage-dev] slow dependency checking

[Brian]

I believe I have found an error in the way porthole is using portage.

After an emerge sync which had a large number of update downloaded.  I
switched to our upgrades view which stated building the treeview.

It was extremely slow, something I had noticed from time to time but did
not know why.  It usually finished before I determined why.  This time
using gnome system monitor I was able to determine that it was portage
doing repeated calls to "ebuild.sh depend" for different packages.

After it is complete a db reload and new upgrades list is quick again.

Am I correct in that the imported instance of portage was still using
the old metadata cache at the time of import? Even though the cache was
updated at the end of the sync.  After a sync we should re-initialize
our instance of portage for it to use the new cache?
-- 
Brian <dol-sen@telus.net>

-- 
gentoo-portage-dev@gentoo.org mailing list

Re: [gentoo-portage-dev] slow dependency checking

[Jason Stubbs]

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On Sunday 12 June 2005 00:34, Brian wrote:
> I believe I have found an error in the way porthole is using portage.
>
> After an emerge sync which had a large number of update downloaded.  I
> switched to our upgrades view which stated building the treeview.
>
> It was extremely slow, something I had noticed from time to time but did
> not know why.  It usually finished before I determined why.  This time
> using gnome system monitor I was able to determine that it was portage
> doing repeated calls to "ebuild.sh depend" for different packages.
>
> After it is complete a db reload and new upgrades list is quick again.
>
> Am I correct in that the imported instance of portage was still using
> the old metadata cache at the time of import? Even though the cache was
> updated at the end of the sync.  After a sync we should re-initialize
> our instance of portage for it to use the new cache?

Correct. I'm not sure what will happen in the future, but adding checks for 
this into the current design will noticably slow down the general case (where 
the cache isn't changed by external processes).

Regards,
Jason Stubbs

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-portage-dev] slow dependency checking

[Jason Stubbs]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

On Sunday 12 June 2005 02:09, Jason Stubbs wrote:
> On Sunday 12 June 2005 00:34, Brian wrote:
> > Am I correct in that the imported instance of portage was still using
> > the old metadata cache at the time of import? Even though the cache was
> > updated at the end of the sync.  After a sync we should re-initialize
> > our instance of portage for it to use the new cache?
>
> Correct. I'm not sure what will happen in the future, but adding checks for
> this into the current design will noticably slow down the general case
> (where the cache isn't changed by external processes).

Incorrect. I checked the code rather than making assumptions and found that it 
is going to disk everytime already - at least in the case of the default flat 
files.

Regards,
Jason Stubbs

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]