-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
MNT: Use micromamba to provision base environment on macOS and Windows #27753
Conversation
Hi! This is the staged-recipes linter and I found some lint. It looks like some changes were made outside the If these changes are intentional (and you aren't submitting a recipe), please add a File-specific lints and/or hints:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR () and found it was in an excellent condition. |
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
With
|
On Windows,
|
Yeah from what I am seeing with mamba / micromamba these days is that there is a non-negligible overhead in parsing the whole repodata. Which is also why lockfiles would shave off a lot. However, later we still need to parse the whole repodata (during the build process), so it moves the cost a little bit (and ideally both processes would use the same cache, and even more ideally a Soon we can hopefully also use the sharded repodata, but that might be a few more months off. Sharded repodata will actually not greatly reduce the cost of downloading (because from my measurements that's pretty much instantly on CI) but the parsing time will be a lot reduced. Pixi / rattler based tools actually do not load the whole repodata but only the subset that's actually needed (which is a good bit faster). Btw. thank you @jaimergp for running these benchmarks! Exciting! |
With micromamba 2.0.2: macOS: 50s
Windows: 1m52s
|
Without simdjson: macOS, 58s:
Windows, 1m53s:
|
Most recent timings for Micromamba v1: macOS, 55s:
Windows (D:), 1m9s:
|
Investigating parts of conda-forge/conda-forge.github.io#2323 (comment)