-
Notifications
You must be signed in to change notification settings - Fork 370
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
mamba 2 solver performance regression #3694
Comments
I am trying to reproduce the performance regression. Currently I cannot reproduce the issue, profiling with
In particular, running the provided command for 2.0.5 gives:
Both takes around 2GiB or RAM to run. The solutions are slightly different: 1c1
< name: 1.5
---
> name: 2.0
53a54
> - boltons=24.0.0=pyhd8ed1ab_1
56c57
< - botorch=0.8.5=pyhd8ed1ab_0
---
> - botorch=0.11.3=pyhd8ed1ab_0
82,83c83,84
< - conda=22.9.0=py311h38be061_2
< - conda-build=3.25.0=py311h38be061_0
---
> - conda=23.7.4=py311h38be061_0
> - conda-build=24.11.2=py311h38be061_1
142a144
> - frozendict=2.4.6=py311h9ecbd09_0
163d164
< - glob2=0.7=py_0
172c173
< - gpytorch=1.13=pyhd8ed1ab_0
---
> - gpytorch=1.12=pyhd8ed1ab_0
219c220
< - jaxtyping=0.2.19=pyhd8ed1ab_0
---
> - jaxtyping=0.2.36=pyhd8ed1ab_0
228a230
> - jsonpatch=1.33=pyhd8ed1ab_1
247c249
< - kernel-headers_linux-64=2.6.32=he073ed8_17
---
> - kernel-headers_linux-64=3.10.0=he073ed8_18
305c307
< - liblief=0.12.3=h27087fc_0
---
> - liblief=0.14.1=h5888daf_2
358c360
< - linear_operator=0.5.3=pyhd8ed1ab_0
---
> - linear_operator=0.5.2=pyhd8ed1ab_0
380a383
> - menuinst=2.2.0=py311h38be061_0
495c498
< - py-lief=0.12.3=py311ha362b79_0
---
> - py-lief=0.14.1=py311hfdbb021_2
515,516c518,519
< - pymc=5.16.1=hd8ed1ab_0
< - pymc-base=5.16.1=pyhd8ed1ab_0
---
> - pymc=5.18.0=hd8ed1ab_0
> - pymc-base=5.18.0=pyhd8ed1ab_0
527,528c530,531
< - pytensor=2.23.0=py311h4332511_0
< - pytensor-base=2.23.0=py311hd037940_0
---
> - pytensor=2.25.2=py311h7babd2d_0
> - pytensor-base=2.25.2=py311h4a3439e_0
574c577
< - ruamel.yaml=0.18.6=py311h9ecbd09_1
---
> - ruamel.yaml=0.17.40=py311h459d7ec_0
576d578
< - ruamel_yaml=0.15.80=py311h459d7ec_1009
581c583
< - scipy=1.14.1=py311he9a78e4_2
---
> - scipy=1.13.1=py311h517d4fd_0
612c614
< - sysroot_linux-64=2.12=he073ed8_17
---
> - sysroot_linux-64=2.17=h4a8ded7_18
631c633
< - typeguard=4.4.1=pyhd8ed1ab_1
---
> - typeguard=2.13.3=pyhd8ed1ab_0 |
Thanks for looking into this! Interesting that you can't reproduce at all. I just tried again on the same system (a VM running Alma Linux 8.7) and got similar results (1h 11min, 7.1 GB with mamba 2.0.5). Then I tried on my laptop (WSL2 running Ubuntu 20.04.6 LTS). Here the difference is smaller but still significant: mamba 1.5.11:
mamba 2.0.5:
So, similar memory usage but still more than 5x slower. Any ideas how to get to the bottom of this? |
Could you provide a YAML environnement specification, all the pieces of configuration, the exact commands again? Alternatively, could you provide runs of |
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
slow
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
Creating an environment with the following spec list is 20x slower with mamba 2.0.5 than with 1.5.11. Memory usage is 2x higher.
mamba info / micromamba info
Logs
No response
environment.yml
No response
~/.condarc
The text was updated successfully, but these errors were encountered: