You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker and believe that this is not a duplicate.
Actual behavior
We did several tries to cache PDM cache on our Gitlab CI and we were surprised of how little it improved pdm sync performances. Until PDM 2.13, PDM was taking 1m57 to install our long list of dependencies, and 1m43 with a filled cache. Cache restauration time on our Gitlab is ~10 secondes so it was not worth it.
With PDM 2.13+, timing moved to 6m20 for an installation with empty cache to 4m35, so yes caching became finally worth it but you see the problem.
Expected behavior
I don't know if this can be fixed/improved. If you think you it can, that's awesome. If you think it's all normal, I'll close the issue.
Actual behavior
We did several tries to cache PDM cache on our Gitlab CI and we were surprised of how little it improved
pdm sync
performances. Until PDM 2.13, PDM was taking 1m57 to install our long list of dependencies, and 1m43 with a filled cache. Cache restauration time on our Gitlab is ~10 secondes so it was not worth it.With PDM 2.13+, timing moved to 6m20 for an installation with empty cache to 4m35, so yes caching became finally worth it but you see the problem.
Expected behavior
I don't know if this can be fixed/improved. If you think you it can, that's awesome. If you think it's all normal, I'll close the issue.
Steps to reproduce
I did a small demonstration repo, pdm-cache-demonstrator , with a very simple reproducible case and long dependencies list, similar to the our production dependencies. There is a
pdm cache info
command before eachpdm sync
, andpdm sync
is run with-v
. We get somewhat similar results that what we experience, but less exacerbated:pdm 2.12.4, empty cache: 1m38
pdm 2.12.4, filled cache: 0m57
pdm 2.13.3, empty cache: 2m37
pdm 2.13.3, filled cache: 2m9
Environment Information
For PDM 2.12:
It would be the same for PDM 2.13
The text was updated successfully, but these errors were encountered: