I see this too, and had filed http://openib.org/bugzilla/show_bug.cgi?id=188 for it. I think Jeff opened a bug in the Open MPI bug tracker for this, he can comment on when it is scheduled to be fixed.
Scott Weitzenkamp SQA and Release Manager Server Virtualization Business Unit Cisco Systems > -----Original Message----- > From: users-boun...@open-mpi.org > [mailto:users-boun...@open-mpi.org] On Behalf Of Maestas, > Christopher Daniel > Sent: Monday, October 16, 2006 7:00 AM > To: us...@open-mpi.org > Subject: [OMPI users] Question on mpi collectives > > How fast/well are MPI collectives implemented in ompi? > I'm running the Intel MPI 1.1. benchmarks and seeing the need to set > wall clock times > 12 hours for run sizes of 200 and 300 > nodes for 1ppn > and 2ppn cases. The collective tests that usually pass in 2ppn cases: > Barrier, Reduce scatter, allreduce, bcast > > The ones that take long or never run: > Allgather, alltoall, allgatherv > > Thanks, > -cdm > > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
