This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On 11 Aug 2010, at 05:10, Randolph Pullen wrote:
> Sure, but broadcasts are faster - less reliable apparently, but much faster for large clusters.
Going off-topic here but I think it's worth saying:
If you have a dataset that requires collective communication then use the function call that best matches what you are trying to do, far to many people try and re-implement the collectives in their own code and it nearly always goes badly, as someone who's spent many years implementing collectives I've lost count of the number of times I've made someones code go faster by replacing 500+ lines of code with a single call to MPI_Gather().
In the rare case that you find that some collectives are slower than they should be for your specific network and message size then the best thing to do is to work with the Open-MPI developers to tweak the thresholds so a better algorithm gets picked by the library.
Ashley Pittman, Bath, UK.
Padb - A parallel job inspection tool for cluster computing