Re: [OMPI users] Concerning the performance of the one-sided communications

How was the latency? That is the best metric to use because osc/pt2pt does put aggregation. Makes the result of osu_put_bw relatively garbage. > On Feb 16, 2018, at 5:24 PM, Jeff Hammond wrote: > > > >> On Fri, Feb 16, 2018 at 8:52 AM, Nathan Hjelm

Re: [OMPI users] Concerning the performance of the one-sided communications

On Fri, Feb 16, 2018 at 8:52 AM, Nathan Hjelm wrote: > It depends on the transport used. If there is a high-performance network > (Cray Aries, Infiniband, etc) then the progress is handled by the hardware. > For other networks (Infinipath, Omnipath, TCP, etc) there are options. >

Re: [OMPI users] MacOS - Running MPI code with 256 procs - “[warn] select: Invalid argument” message

Hello Gilles, I have upgraded to OS X 10.13.3 High Sierra but still have no luck with my issue. To increase the limit of open files, from this link I did : 1) *sudo vim

Re: [OMPI users] Concerning the performance of the one-sided communications

It depends on the transport used. If there is a high-performance network (Cray Aries, Infiniband, etc) then the progress is handled by the hardware. For other networks (Infinipath, Omnipath, TCP, etc) there are options. For TCP you can set:  --mca btl_tcp_progress_thread 1 No such option

[OMPI users] Concerning the performance of the one-sided communications

Hi all, I used to work with MPICH. I am trying now to compare and switch to OpenMPI. I am using OpenMPI version 2.1.1. To have progress for one-sided communications (in the passive mode). I used to export the following environment variable MPICH_ASYNC_PROGRESS=1 My questions are: 1. What would