Tad Lake wrote:
I run it :
mpirun -np 2 --host node2 ./a.out
But the result of time is not stable with difference of 100 times. For example,
the max value of time can be 3000, meanwhile the min is 100.
Again, know what results to expect. Is 3000 a reasonable time and 100
too fast? Or, is
Mark Potts wrote:
Hi,
I'd opt for the fact that tv0 is given value only on rank 0 and
tv1 is
only given value on rank 1. Kind of hard to get a diff betwn the two
on either rank with that setup. You need to determine the tv0 and
tv1
on both ranks.
I don't understand this.
Hi,
I'd opt for the fact that tv0 is given value only on rank 0 and tv1 is
only given value on rank 1. Kind of hard to get a diff betwn the two
on either rank with that setup. You need to determine the tv0 and tv1
on both ranks.
In addition, there are a number of other errors in t
Did you bind the processes? If not you may be seeing the impact of having
processes bouncing between cpus, and/or processes not being local to their
memory. Try adding -bind-to-core or -bind-to-socket to your cmd line and see if
things smooth out. I'm assuming, of course, that you are running on
Hi,
I have a little program for execution time.
=
#include "mpi.h"
#include
#include
#include
#include
int main (int argc, char *argv[]) {
MPI_Status Stat;
struct timeval tv0, tv1;
long int totaltime = 0;
int i, j;
int buf[10240];
