[Paraview] [EXTERNAL] Re: Paraview crashing when clipping an openfoam solution

[Carlos E Manglano-Villamarin]

>
>
>    - Run View/ Memory Inspector.  As you do stuff, watch memory grow.
>    Does it look like memory is growing until PV dies? *Starting with
>    53.6% of RAM free, no swapping.*
>
>
>    - Minimize the size of your dataset.  Although you only have a million
>    cells (rounding), how many variables to you have?  Don’t load (or don’t
>    create) variables that you don’t need. *410175 cells, and loading 'p'
>    and 'U' only*
>
>
>    - How many blocks do you have?  If the answer is lots (hundreds?), I
>    believe this creates memory pressure. *blocks? I guess the answer is:
>    just one block. I reconstruct latestTime after simulation*
>
>
>    - Do you have sidesets/ edgesets?  Don’t load these unless needed (as
>    you can see, I don’t know openfoam). *No sets loaded*
>
>
>    - Run top.  How big is ParaView getting? *Starts with 3.8%. Then it
>    goes up to 10.4% when loading the *.OpenFOAM file (statistics information
>    says 82MB) And, system monitor says PV is using 448.4MB. **When I
>    create a clip, the memory used by PV, as said by System Monitor, goes up to
>    519.7MB. Top says PV is using 11.6% of memory.*
>
>
>    - Try opening your data with no variables loaded.  What is the memory
>    inspector doing? *System Monitor shows 63.8MB used by paraview before
>    loading foam case. And, 336.2MB when loading the case with no variables,
>    just the internalMesh.*
>
>
>    - How much hardware do you have on your computer?  If it’s a new
>    computer with 8 GBytes, that is very different than an old converted
>    machine with .25GBytes. *Motherboard 9 year old computer with 6GB of
>    RAM, which have not given me ANY problem until last few days.*
>
>
>    - Try looking at your memory footprint (memory inspector, top) BEFORE
>    applying filters.  Every filter you use increases memory. *Memory
>    footprint doesn't increase dangerously.*
>
>
>    - Use filters such as slice (i.e., 2d) rather than clip (3d), and
>    contour (2d) rather than clip by scalar.  What I mean here is to create a
>    surface, rather than a solid.  Surfaces use less memory. *That's a
>    good walk around, thanks!*
>
>
>    - Don’t volume render.  It really sucks memory. *Volume render? You
>    mean, like 'streamlines'?*
>
> *Thank very much Shawn!!! i really appreciate your help.*
>

Carlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180326/15d35daa/attachment.html>