Hello Miguel,
On Friday 25 August 2006 15:40, Miguel Figueiredo Mascarenhas Sousa Filipe
wrote:
> Hi,
>
> On 8/25/06, Sven Stork wrote:
> >
> > Hello Miguel,
> >
> > this is caused by the shared memory mempool. Per default this shared
> > memory
> > mapping has a size of 512 MB. You can use th
Hi,
On 8/25/06, Sven Stork wrote:
Hello Miguel,
this is caused by the shared memory mempool. Per default this shared
memory
mapping has a size of 512 MB. You can use the "mpool_sm_size" parameter to
reduce size e.g.
mpirun -mca mpool_sm_size ...
using
mpirun -mca mpool_sm_size 0
is acce
I suspect this is the shared memory used to communicate between processes.
Please run your application adding the flag "--mca btl tcp,self" to the
mpirun command line (*before the application name). If the virtual memory
usage goes down then the 400MB are definitively comming from the shared
me
Hello Miguel,
this is caused by the shared memory mempool. Per default this shared memory
mapping has a size of 512 MB. You can use the "mpool_sm_size" parameter to
reduce size e.g.
mpirun -mca mpool_sm_size ...
Thanks,
Sven
On Friday 25 August 2006 15:04, Miguel Figueiredo Mascarenhas Sousa
Hi there,
I'm using openmpi-1.1 on a linux-amd64 machine and also a linux-32bit x86
chroot environment on that same machine.
(distro is gentoo, compilers: gcc-4.1.1 and gcc-3.4.6)
In both cases openmpi-1.1 shows a +/-400MB overhead in virtual memory usage
(virtual address space usage) for each MP
