Let's keep this on the user list so others with similar issues can find it.
My guess is that the $OMP_NUM_THREADS syntax isn't quite right, so it didn't
pick up the actual value there. Since it doesn't hurt to have extra cpus, just
set it to 8 for your test case and that should be fine, so addin
I would suggest having him look at the core file with a debugger and see where
it fails. Sounds like he has a memory corruption problem.
On Jun 24, 2014, at 3:31 AM, Dr.Peer-Joachim Koch wrote:
> Hi,
>
> one of our cluster users reported a problem with openmpi.
> He created a short sample (ju
OMPI started binding by default during the 1.7 series. You should add the
following to your cmd line:
--map-by :pe=$OMP_NUM_THREADS
This will give you a dedicated core for each thread. Alternatively, you could
instead add
--bind-to socket
OMPI 1.5.5 doesn't bind at all unless directed to do s
Hello!
I have open mpi 1.9a1r32104 and open mpi 1.5.5.
I have much better perfomance in open mpi 1.5.5 with openMP on 8 cores
in the program:
#define N 1000
int main(int argc, char *argv[]) {
...
MPI_Init(&argc, &argv);
...
for (i = 0; i < N; i++) {
a[i] = i * 1.
