Thank you for your patience.
Best wishes !
Gilles Gouaillardet 于2018年12月16日周日
下午11:24写道：
> Almost :-)
>
> seqBegin() and seqEnd() takes a communicator as a parameter.
> So attribute caching is good for performance (only) if more than one
> sequence *per communicator* is used in the application
Almost :-)
seqBegin() and seqEnd() takes a communicator as a parameter.
So attribute caching is good for performance (only) if more than one
sequence *per communicator* is used in the application.
Cheers,
Gilles
On Sun, Dec 16, 2018 at 11:38 PM 邹海峰 wrote:
>
> Thank you very much for the reply.
I'm running OpenMPI 2.1.0 on RHEL 7 using TCP communication. For the
specific run that's crashing on me, I'm running with 17 ranks (on 17
different physical machines). I've got a stage in my application where
ranks need to transfer chunks of data where the size of each chunk is
trivial (on the or
Thank you very much for the reply.
According to your explanation and the content from the website, if there is
only one sequential execution in the program, then it doesn't matter
whether using the attribute. But if there are multiple sequential
execution, each process only needs to use MPI_Comm_
