sburg, MD 20899
Office: 223/A131 or (301) 975-2889
*From:* fipy-boun...@nist.gov on behalf of
Michael Waters
*Sent:* Tuesday, October 11, 2016 4:55:51 PM
*To:* FIPY
*Subject:* Re: Memory Leaks with Trilinos
Hi Trevor,
My mystery deepens. Today, I've compiled
23/A131 or (301) 975-2889
From: fipy-boun...@nist.gov on behalf of Michael Waters
Sent: Tuesday, October 11, 2016 4:55:51 PM
To: FIPY
Subject: Re: Memory Leaks with Trilinos
Hi Trevor,
My mystery deepens. Today, I've compiled and tried the following combinati
you test the next incremental version (11.10.2)?
Trevor
From: fipy-boun...@nist.gov on behalf of Michael Waters
Sent: Wednesday, March 30, 2016 4:36 PM
To: FIPY
Subject: Re: Memory Leaks with Trilinos
Hi Jon,
I just compiled an old version of swig (2
: Re: Memory Leaks with Trilinos
No worries. If building trilinos doesn't blindside you with something
unexpected and unpleasant, you're not doing it right.
I have a conda recipe at
https://github.com/guyer/conda-recipes/tree/trilinos_upgrade_11_10_2/trilinos
that has worked for m
Hi Jon,
I just compiled an old version of swig (2.0.8) and compiled Trilinos
(11.10.1) against that. Sadly, I am still having the leak.
I am out of ideas for the day... and should be looking for a post doc
anyway.
Thanks,
-mike
On 3/30/16 3:32 PM, Guyer, Jonathan E. Dr. (Fed) wrote:
> No wor
FYI, the Docker installation for FiPy: https://github.com/wd15/fipy-dockerize
On Wed, Mar 30, 2016 at 3:32 PM, Guyer, Jonathan E. Dr. (Fed)
wrote:
> No worries. If building trilinos doesn't blindside you with something
> unexpected and unpleasant, you're not doing it right.
>
> I have a conda re
No worries. If building trilinos doesn't blindside you with something
unexpected and unpleasant, you're not doing it right.
I have a conda recipe at
https://github.com/guyer/conda-recipes/tree/trilinos_upgrade_11_10_2/trilinos
that has worked for me to build 11.10.2 on both OS X and Docker (Deb
Hi Jon,
I was just reviewing my version of Trilinos 11.10 and discovered that
there is /no way/ that I compiled it last night after exercising. It has
unsatisfied dependencies on my machine. So I must apologize, I must have
been more tired than I thought.
Sorry for the error!
-Mike Waters
O
Hi Jon,
I was just reviewing my version of Trilinos 11.10 and discovered that
there is /no way/ that I compiled it last night after exercising. It has
unsatisfied dependencies on my machine. So I must apologize, I must have
been more tired than I thought.
Sorry for the error!
-Mike Waters
O
My plots are in KiBs, not MiBs (I didn't do anything to post-process the output
of syrupy). >10 GiB for 1.3 M cells is consistent with our typical (excessive)
memory usage.
We've been using Trilinos for a long time (~10 years?) so if you can manage to
build them, you can try Trilinos versions g
Hi Jon,
Last night, I compiled and tried Trilinos 11.10 from the Trilinos git
repo, I am still getting the memory leak. I see it in both RSS and
VSIZE. Looking back at your memory numbers from your previous email,
they seem too small for even storing the float data for all the cells.
The slo
It looked to me like steps and accuracy were the way to do it, but my runs
finish in one step, so I was confused. When I change to accuracy = 10.0**-6, it
takes 15 steps, but still no leak (note, the hiccup in RSS and in ELAPSED time
is because I put my laptop to sleep for awhile, but VSIZE is r
When I did my testing and made those graphs, I ran Trilinos in serial.
Syrupy didn't seem to track the other processes memory. I watched in
real time as the parallel version ate all my ram though.
To make the program run longer while not changing the memory:
steps = 100 # increase this, (limit
I guess I spoke too soon. FWIW, I'm running Trilinos version: 11.10.2.
On Mar 29, 2016, at 3:34 PM, Guyer, Jonathan E. Dr. (Fed)
wrote:
> I'm not seeing a leak. The below is for trilinos. VSIZE grows to about 11 MiB
> and saturates and RSS saturates at around 5 MiB. VSIZE is more relevant for
I'm not seeing a leak. The below is for trilinos. VSIZE grows to about 11 MiB
and saturates and RSS saturates at around 5 MiB. VSIZE is more relevant for
tracking leaks, as RSS is deeply tied to your system's swapping architecture
and what else is running; either way, neither seems to be leaking
> Office: 223/A131 or (301) 975-2889
>
>
> ________
> From: fipy-boun...@nist.gov on behalf of Michael
> Waters
> Sent: Monday, March 28, 2016 2:10 PM
> To: FIPY
> Subject: Re: Memory Leaks with Trilinos
>
> Thanks, If you think DFT
: 223/A131 or (301) 975-2889
From: fipy-boun...@nist.gov on behalf of Michael Waters
Sent: Monday, March 28, 2016 2:10 PM
To: FIPY
Subject: Re: Memory Leaks with Trilinos
Thanks, If you think DFT in FiPy is strange, you should see how I make
isosurfaces i
Thanks, If you think DFT in FiPy is strange, you should see how I make
isosurfaces in POV-Ray. :)
That said, If anyone is tinkering with my example and has questions, I
am glad to answer them!
Cheers,
-Mike Waters
On 03/28/2016 01:46 PM, Guyer, Jonathan E. Dr. (Fed) wrote:
> Mike, thanks for
Mike, thanks for the example, and for the rather perverse application of FiPy!
I'll fiddle with this and see what I get.
- Jon
On Mar 25, 2016, at 7:16 PM, Michael Waters wrote:
> Hello,
>
> I still have a large memory leak when using Trilinos. I am not sure where to
> start looking so I mad
Hello,
I still have a large memory leak when using Trilinos. I am not sure
where to start looking so I made an example code that produces my
problem in hopes that someone can help me.
But! my example is cool. I implemented *Density Functional Theory in FiPy!**
*My code is slow, but runs in p
20 matches
Mail list logo
