poetry: 1.2 performance regression

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Issue

I mentioned this in Discord, but didn’t want it to get lost in the shuffle. I put together a Python package manager benchmark. I got a suggestion to add the current prerelease to the test suite.

Preliminary results showed the same operations taking ~2x the time vs. the non prerelease version. You can see results here: https://github.com/lincolnloop/python-package-manager-shootout/actions/runs/2705531257

Compare elapsed time between poetry and poetry-pre:

image

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

@radoering with the current poetry branch the total installation times got on par with the poetry v1.1.15:

  • dependency resolution stays at 0.8s
  • remaining installation time improved significantly or is even a bit faster than poetry v1.1.15
action v1.1.5 v1.2 branch12
update dependencies 0.3s 0.8s 0.8s
clean install 13.5s 29s 13.s

Anyway, when I run the test with the poetry from branch 1.2, the second attempt got stuck and I had to kill it after 2 minutes. This happened only once, later attempts to repeat the installation did not fail.

Note: by “clean install” I mean

  1. clean the virtualenv and poetry.lock file first $ rm -rf .venv *.lock
  2. and then run the $ poetry install