33
4096 50 5921.50 0.66
8192 50 5953.92 1.31
16384 50 6025.42 2.59
32768 50 6172.76 5.06
65536 50 6459.50 9.68
131072 50 7037.1017.76
262144 50 8216.8130.43
524288 50 10614.9047.10
1048576 50 15415.3564.87
2097152 50 25000.1180.00
4194304 50 44130.7890.64
8388608 50 82288.7997.22
16777216 50158273.73 101.09
george.
On Apr 28, 2008, at 1:20 PM, jean-christophe.mig...@ens-lyon.fr wrote:
Hi all,
We're using a pingpong in order to measure the bandwidth and latency
available with open MPI.
In our first experiments done with the 1.1.4 version, we were using the
btl_tcp_eager_limit parameter to modify the eager limit. We've upgraded
to the 1.2.6 version and the limit parameter we fix doesn't seem to be
taken in account. The value we want to use is 67108864. The command
line is:
mpirun -np 2 -machinefile node_file -mca btl_tcp_sndbuf 4194304 -mca
btl_tcp_rcvbuf 4194304 -mca btl_tcp_eager_limit 67108864 pingpong.
Is this parameter still useful (ompi_info shows that this parameter is
still available) ?
Does anybody have any idea ?
Thanks in advance.
JC Mignot and Ludovic Hablot
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
