Regarding performance, we have example of code using Anaconda-provided
packages that run 10 times slower than the same code using locally built
packages, optimized for the cluster architectures. That's not *a bit*
slower, that's a lot slower.
Regarding "cheating on your partner", that analogy is not by me, but the
point he is trying to carry is that Anaconda basically replaces any
cluster provided versions, which HPC center people are working hard to
optimize. Recent versions of Anaconda are even worse, by packaging
things like compilers and linkers, creating conflicts with
cluster-provided system libraries and tools, and creating a lot of
debugging problems for users and support people alike.
Regards,
Maxime
On 2018-08-28 12:48 PM, Rémi Rampin wrote:
2018-08-28 12:27 EDT, Maxime Boissonneault
<[email protected]
<mailto:[email protected]>>:
As a side-discussion, I think we should also be wary of using
Anaconda,
and tell users not to use it in a cluster environment. For
reasons, see
here :
https://twitter.com/mboisso/status/1034476890353020928
Hi Maxime,
All I see in this thread is that "it's like cheating on your partner"
(!!!) and it's "generically optimized software" that might be a bit
slower than locally-built libs (interesting concern when using Python,
an interpreted scripting language (and on the slow side too)).
Could you elaborate on those reasons?
Best
--
Rémi
------------------------------------------
The Carpentries: discuss
Permalink:
https://carpentries.topicbox.com/groups/discuss/T1505f74d7f6e32f8-Mb3de150d1dd911032d34b1e8
Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
