Generating lockfiles takes 22 minutes for our repo...
# generalb
blue-football-92560
03/13/2023, 5:49 PMGenerating lockfiles takes 22 minutes for our repo. Is there a way to speed it up? Or at least get a rough idea of what is taking the most time?
Copy code
generate-lockfiles 0.27s user 0.05s system 0% cpu 22:26.65 total Copy code
pip install --no-cache-dir -r requirements.txt 268.47s user 34.02s system 89% cpu 5:38.85 totalh
high-yak-85899
03/13/2023, 5:51 PMBuilding a virtual environment and generating a lockfile are two very different things
high-yak-85899
03/13/2023, 5:51 PMThe former pins exact versions for all packages to a consistent state according to all transitive dependencies of every required package
high-yak-85899
03/13/2023, 5:52 PMThe latter is just pip going through dependency by dependency and installing something that meets the bounds specified
high-yak-85899
03/13/2023, 5:52 PMIt will gladly clobber other installs and create an end result that does not meet the needs of all the packages in the ecosystem (though it still may just work).
high-yak-85899
03/13/2023, 5:53 PMWhen this gets asked, the first place to look is how your interpreter constraints are set in
pants.tomlhigh-yak-85899
03/13/2023, 5:54 PMThere are quite a few threads in here already that will give some insight on how to check if things are poorly conditioned. So those will be a good first place to look.
high-yak-85899
03/13/2023, 5:55 PMAnother good thread to read up on this for just the general challenge of the problem and things that take long even with a well-conditioned environment is here.