<div class="gmail_quote">On Fri, Dec 23, 2011 at 16:36, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":32q">I tried all of your suggestions, unfortunately, still get MUMPS not<br>
moving an inch. Running in debugger and interrupting reveals:<br>
<br>
0x000000000139d233 in dgemm (transa=..., transb=..., m=3621, n=3621, k=251,<br>
alpha=-1, a=..., lda=3872, b=..., ldb=3872, beta=1, c=..., ldc=3872,<br>
_transa=1, _transb=1) at dgemm.f:242<br>
242 C(I,J) = C(I,J) + TEMP*A(I,L)<br>
<br>
So it's seems to be doing something, but on a small problem it takes a<br>
few minutes, so I do not expect a problem of 2-3 times the size take<br>
longer than a day...</div></blockquote></div><br><div>Is one mesh just a refined version of the other, or is the shape different? Factorization time should be roughly quadratic in problem size for 3D problems.</div><div>
<br></div><div>If the increased fill caused the system to run out of physical memory and start swapping, then it would not be surprising for it to take days.</div>