Rolf - this doesn’t sound right to me. I assume that smcuda is only supposed to build if cuda support was found/requested, but if there are no cuda adapters, then I would have thought it should disqualify itself.
Can we do something about this for 1.8.6? > On May 20, 2015, at 11:14 AM, Aurélien Bouteiller <boute...@icl.utk.edu> > wrote: > > I was making basic performance measurements on our machine after installing > 1.8.5, the performance were looking bad. It turns out that the smcuda btl has > a higher exclusivity than both vader and sm, even on machines with no nvidia > adapters. Is there a strong reason why the default exclusivity is set so high > ? Of course it can be easily fixed with a couple of mca options, but > unsuspecting users that “just run” will experience 1/3 overhead across the > board for shared memory communication according to my measurements. > > > Side note: from my understanding of the smcuda component, performance should > be identical to the regular sm component (as long as no GPU > operation are required). This is not the case, there is some performance > penalty with smcuda compared to sm. > > Aurelien > > -- > Aurélien Bouteiller ~~ https://icl.cs.utk.edu/~bouteill/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/05/17435.php
