We experience an aging problem with lam-6.5.6 on a Sun workstation cluster.
Since we run the same code using MPICH and a native MPI version on Suns, HPs
and Linux I doubt that this is a problem related to our code. Has anybody
experienced suche a behaviour?
time steps | CPU time/iteration
40 | 107
45 | 123
50 | 138
63 | 175
and so on. During iterations going from one multigrid level to the next (we
have a grid based flow solver) this behaviour starts to start from scratch,
but there are no special MPI calls during this transient.
I would appreciate any help on how to debug such a thing and what could be
the reason for this.
Holger
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|