Hello,
I noticed this weird behavior, because after a certain time of more than
one minute the transfer rates of MPI_Send and MPI_Recv dropped by a
factor of 100+. By chance I saw, that my program did allocate more and
more memory. I have the following minimal working example:
#include
Hello,
After compiling and running a MPI program, it seems to hang at
MPI_Init(), but it eventually will work after a minute or two.
While the problem occured on my Notebook it did not on my desktop PC.
Both run on Win 7, cygwin 64 Bit, OpenMPI version 1.8.3 r32794
(ompi_info), g++ v 4.8.3.
Hello,
After compiling and running a MPI program, it seems to hang at
MPI_Init(), but it eventually will work after a minute or two.
While the problem occured on my Notebook it did not on my desktop PC.
It can be a timeout on a network interface.
I see a similar issue with wireless ON but no
It doesn't seem to work. (switching off wlan still works)
mpicc mpiinit.c -o mpiinit.exe; time mpirun --mca btl sm,self -n 2
./mpiinit.exe
real0m43.733s
user0m0.888s
sys 0m0.824s
Am 28.10.2014 13:40, schrieb Jeff Squyres (jsquyres):
On Oct 27, 2014, at 1:25 PM, maxinat
Hello again,
I have a piece of code, which worked fine on my PC, but on my notebook
MPI_Wtime and MPI_Wtick won't work with the -mno-sse flag specified.
MPI_Wtick will return 0 instead of 1e-6 and MPI_Wtime will also return
always 0. clock() works in all cases.
The Code is:
#include
#inclu
