On Aug 7, 2008, at 3:20 AM, Jan Ploski wrote:
http://www.open-mpi.org/community/lists/users/2008/07/6161.php
Thanks for this explanation. According to what you wrote,
--without-memory-manager can make my and other applications run
significantly slower.
*If* they continually re-use the s
users-boun...@open-mpi.org schrieb am 08/07/2008 09:27:39 AM:
> I can't speak for Jeff, but my understanding of the changes for 1.3
> should allow you to switch off the memory manager when running your
> checks.
>
> It seems to me an obvious interim solution would be to have two versions
> of Ope
I can't speak for Jeff, but my understanding of the changes for 1.3
should allow you to switch off the memory manager when running your
checks.
It seems to me an obvious interim solution would be to have two versions
of OpenMPI installed, one with and one without the memory manager. Use
one for d
users-boun...@open-mpi.org schrieb am 08/06/2008 07:44:03 PM:
> On Aug 6, 2008, at 12:37 PM, Jan Ploski wrote:
>
> >> I'm using the latest of Open MPI compiled with debug turned on, and
> >> valgrind 3.3.0. From your trace it looks like there is a conflict
> >> between two memory managers. I'm
On Aug 6, 2008, at 12:37 PM, Jan Ploski wrote:
I'm using the latest of Open MPI compiled with debug turned on, and
valgrind 3.3.0. From your trace it looks like there is a conflict
between two memory managers. I'm not having the same problem as I
disable the Open MPI memory manager on my bu
George Bosilca wrote:
Jan,
I'm using the latest of Open MPI compiled with debug turned on, and
valgrind 3.3.0. From your trace it looks like there is a conflict
between two memory managers. I'm not having the same problem as I
disable the Open MPI memory manager on my builds (configure option
Jan,
I'm using the latest of Open MPI compiled with debug turned on, and
valgrind 3.3.0. From your trace it looks like there is a conflict
between two memory managers. I'm not having the same problem as I
disable the Open MPI memory manager on my builds (configure option --
without-memory-
users-boun...@open-mpi.org schrieb am 08/05/2008 05:51:51 PM:
> Jan,
>
> I'm using valgrind with Open MPI on a [very] regular basis and I never
> had any problems. I usually want to know the execution path on the MPI
> applications. For this I use:
> mpirun -np XX valgrind --tool=callgrind -q -
One tip is to use the --log-file=valgrind.out.%
q{OMPI_MCA_ns_nds_vpid} option to valgrind which will name the output
file according to rank. In the 1.3 series the variable has changed from
OMPI_MCA_ns_nds_vpid to OMPI_COMM_WORLD_RANK.
Ashley.
On Tue, 2008-08-05 at 17:51 +0200, George Bosilca w
Jan,
I'm using valgrind with Open MPI on a [very] regular basis and I never
had any problems. I usually want to know the execution path on the MPI
applications. For this I use:
mpirun -np XX valgrind --tool=callgrind -q --log-file=some_file ./my_app
I just run your example:
mpirun -np 2
Hi,
I wanted to determine the peak heap memory usage of each MPI process in my
application. Using MVAPICH it can be done by simply substituting a wrapper
shell script for the MPI executable and from that wrapper script starting
"valgrind --tool=massif ./prog.exe". However, when I tried the same
11 matches
Mail list logo
