-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve can be slow for specific packages #2134
Comments
@synapticarbors from #1873 to here, maybe related to mamba-org/resolvo#49. |
Thanks for the information! This was merged some time ago which has resulted in better results in some cases but we're now seeing some edge cases where it got much slower. FYI @baszalmstra Tip While we're working on improving the speed. You can always add more constrained requirements to help the solver avoid unwanted paths in the traversal of the solution space. A good one to always add is the minimal version of |
I can confirm that upgrading to Here is my
HTH |
This takes 40minutes to solve with 0.30.0
|
This was fixed in #2162, Thanks for providing examples that helped a lot! |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
save this as
environment.yml
, then solve it withIssue description
Solve takes a long time (90s on my machine), as a comparsion,
conda-lock
takes 55sExpected behavior
The solve should not be that slow, or at least as fast as
conda-lock
The text was updated successfully, but these errors were encountered: