Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

From: Scott Weitzenkamp \(sweitzen\) (sweitzen_at_[hidden])
Date: 2006-10-16 11:23:31

I see this too, and had filed 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-bounces_at_[hidden]
> [mailto:users-bounces_at_[hidden]] On Behalf Of Maestas,
> Christopher Daniel
> Sent: Monday, October 16, 2006 7:00 AM
> To: users_at_[hidden]
> 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
> users_at_[hidden]