Closed wm75 closed 2 years ago
Ooh oh, #101 got opened in parallel while I was putting this together. Go with whichever version you like best and sorry about that.
I'll close mine, yours is so much better written! Maybe it's also worth pinging mamba
folks about this? Inconsistency between mamba
and conda
is something they try to avoid I think.
FWIW, if Open MPI is built with plugins (default in the v4 series), it is possible to put the UCX related plugins (e.g. mca_pml_ucx.so
, mca_btl_uct.so
and mca_osc_ucx.so
) in a separate packages (e.g. openmpi-ucx
).
So if you do not need for UCX (long story short, you do not run on an infiniband network), you would not have to pull UCX and (indirectly) CUDA.
Solution to issue cannot be found in the documentation.
Issue
With the latest linux-64 openmpi builds ucx has started appearing as a dependency, instead of just a constraint:
So ucx was constrained-only in
openmpi 4.1.3 hbea3300_101
, but is a dependency inopenmpi 4.1.3 h846660c_102
andopenmpi 4.1.3 h846660c_103
. Not sure how/why that happened, but since ucx depends oncudatoolkit
this creates an indirect dependency for openmpi, too, and results in substantially bigger environments as noted by users of the pangolin tool for SARS-CoV-2 lineage assignment here: https://github.com/cov-lineages/pangolin/issues/441.Note: For some even more obscure reason,
cudatoolkit
gets resolved as a dependency only by mamba, but not by conda.I don't understand enough about the interdependencies to call this a bug, but it's an inconvenience that would be super nice to have resolved if possible.
Installed packages
Environment info