Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 917260 - sys-apps/portage-3.0.51: does dependency resolution timer include waiting for lockfile?
Summary: sys-apps/portage-3.0.51: does dependency resolution timer include waiting for...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-12 18:18 UTC by lekto
Modified: 2023-11-12 21:54 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lekto 2023-11-12 18:18:39 UTC
Hi, I was installing Gentoo on older laptop on thumbdrive with poor iops. I got this when bash-completion was installing in background (I was looking at use flags):
> livecd ~ # emerge -pev @world
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies   * waiting for lock on /var/db/.pkg.portage_lockfile ...
>                    [ ok ]
> ... done!
> Dependency resolution took 348.50 s.

Nearly 6min on system with barely anything more than basic stage 3 is stupidly long. I run this again after bash-completion was already installed and got:
> livecd ~ # emerge -pev @world 
> 
> These are the packages that would be merged, in order:
> Calculating dependencies... done!
> Dependency resolution took 12.43 s.

Looks like dependency resolution includes waiting for lockfile, which isn't feel right.
Comment 1 Zac Medico gentoo-dev 2023-11-12 21:54:01 UTC
We can time this lock and subtract it out:

> lib/_emerge/FakeVartree.py:                self._real_vardb.lock()