[mvapich-discuss] MVAPICH and MOLCAS

[Matthew Koop]

Pawel,

By 'subsequent jobs', what do you mean? If the process has exited and the
memory is still free'd we have not heard of such a problem with our
library.

In the 1.1 branch we have made changes to help with issues where the MPI
library was shown to be using too much memory (and failing in some cases).
In this case a 'free' was not really unpinning memory immediately, so a
'free' immediately followed by a large malloc (and touching of that
buffer) could run the machine out of memory.

If you think this might be the problem then the following place is where
you can download the latest tarball:

http://mvapich.cse.ohio-state.edu/nightly/mvapich/branches/1.1

>From your description though I think it may be a GA issue.

Matt

On Tue, 9 Jun 2009, Pawel Dziekonski wrote:

> On Tue, 09 Jun 2009 at 10:33:54AM -0400, Dhabaleswar Panda wrote:
> > Which version of MVAPICH are you using? Have you tested your application
> > with the latest MVAPICH 1.1 version - the version from 1.1 bugfix branch.
> > You can access it from MVAPICH download page. This version is also
> > available with OFED 1.4.1. The latest version includes a fix related to
> > unregistering stale memory registration.
>
> Can you write more about this problem or point me to some bug reports?
> I was recently observing a king of lost memory after specific jobs.
> This memory can't be allocated by subsequent jobs. Pure malloc clears it.
>
> Regarding MOLCAS - after further investigation I think it's prpbably
> a problem with Global Arrays.
>
> regards, P
> --
> Pawel Dziekonski <pawel.dziekonski at wcss.pl>
> Wroclaw Centre for Networking & Supercomputing, HPC Department
> Politechnika Wr., pl. Grunwaldzki 9, bud. D2/101, 50-377 Wroclaw, POLAND
> phone: +48 71 3202043, fax: +48 71 3225797, http://www.wcss.wroc.pl
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>