Making conda fast again

You might have seen the announcement on Twitter: at QuantStack we’ve been working on making a prototype of a conda-compatible package manager called mamba. Conda is a great tool to distribute data science packages. The community-led conda-forge comprises tons of awesome packages. The Anaconda company supplies us with recent and well integrated compilers. And conda-build is simply amazing to build binaries across different platforms (Windows, Linux and OS X). At QuantStack we use conda all the time to package Python, C++, Julia and R packages, and ship them to clients around the world.

However, due to the growth of conda-forge (it’s got over 60'000 packages for Linux right now) many users have made experience with the “conda: Solving environment” spinner. It’s been frustratingly slow for a while now.

At QuantStack, one of our main expertises is building High Performance applications for customers, mainly using C++.

To make conda faster we propose to

  • Build a Python extension using C++, pybind11 and compile it with all optimizations enabled
  • Use the existing libsolv library, that powers package managers like Fedora’s DNF or OpenSUSEs zypper and (like conda) performs SAT solving to satisfy all package dependencies correctly
  • For faster parsing of the repodata.json (already 35 MB of JSON for conda-forge) we use a library called simdjson which enables high speed parsing

With the prototype, we manage to solve environments in seconds, as demonstrated in the following video:

This prototype is already available on conda-forge. Existing conda users can install it easily by executing

conda install mamba -c conda-forge/label/mamba-alpha -c conda-forge

The source code for all of mamba can be found on github:

The code is re-using as much from conda as possible. We re-implemented only the repository parsing, and the solving. Thanks to using the existing libsolv abstractions, mamba’s total lines of code are roughly 300 lines of Python, mostly adapted from conda, and 600 lines of C++ for parsing the JSON and adding all rules to libsolv. We try to keep this library as small as possible, which also makes it easier to debug and reason about.

We’re currently ironing out some low-hanging bugs, but actively looking into ways to further fund this work. We already have some promising leads, but if you know of an organization or company willing to sponsor some days of development for these tools, that would be great. We’re doing this with the goal of upstreaming the work into the original conda package manager at some point in the future.

Until this happens: the Anaconda team has also released a very interesting blog post with tips on how to make conda faster

                  __    __    __    __
/ \ / \ / \ / \
/ \/ \/ \/ \
███████████████/ /██/ /██/ /██/ /█████████████████████████████
/ / \ / \ / \ / \ \____
/ / \_/ \_/ \_/ \ o \__,
/ _/ \_____/ `

Ongoing work

We still have some work to do:

  • libsolv has never been run on Windows before we at QuantStack made a Windows port week ago. We’re currently upstreaming the changes. Just in case you know the equivalent of fcntl(store->pagefd, F_SETFD, FD_CLOEXEC); on Windows we’d glad to hear from you on this PR
  • Thankfully, the libsolv maintainers (especially Michael Schroeder) have already implemented conda version matching exactly to the Python specifications (! However, we have not yet had the time to make use of it. We definitely need to integrate this work to get the exact version ordering as expected from conda.
  • We need to verify that the conda test suite is passing so that we get a chance at upstreaming this work eventually. This includes evaluating the optimization strategies used by libsolv vs conda.
  • Cache parsed repository data into .solv files, the libsolv binary format. Using this caching format makes repo loading a matter of milliseconds.

About QuantStack

QuantStack is located in the center of Europe (Paris). We build Open Source Software for a living — from creating fresh conda packages to robot applications, from high performance computing to interactive C++ and Jupyter widgets. If you’re interested in our services, do not hesitate to drop us a line.




I work as a scientific and robotics software developer for QuantStack in Paris and Berlin. We do Open Source for a living!

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Python Objects: Under the Hood

Unit tests ain’t about correctness

READ/DOWNLOAD#( C++ for Engineers and Scientists F

Post-mortem: 29 Jan options exercise bug

MongoDB explain() explained

explain with executionStats

4 Ways to Check Email Flow using SMTP Commands

6 Fun/Weird Python Packages to keep you entertained during the quarantine

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Wolf Vollprecht

Wolf Vollprecht

I work as a scientific and robotics software developer for QuantStack in Paris and Berlin. We do Open Source for a living!

More from Medium

Python 2 vs Python 3 — Which is better?

What is in the eScience toolbox: Stef on his favourite meshing library

Intro to Python ast Module

Visualize your multiprocessing calculations in python with parallelbar module