[Paraview] [EXT] Re: Linux memory problems exclusive to Paraview

Dennis Conklin dennis_conklin at goodyear.com
Thu Jan 21 14:09:22 EST 2016


David,

I have attached the summary from top – it indicates that of my 32GB, 5.4 GB is “free”.   Note that nothing is actually “using” that much memory.   If I run Paraview with my huge model, then it will be very slow and complain about not having memory.   If I run other programs to process this huge model, they will work just fine and never notice that they don’t have memory.   It appears that they can access the “used” memory while paraview cannot use it.

The distribution info is also attached.

We are not yet compiling Paraview here – we are using the v4.4 Linux 64-bit executables DL’ed from the website, so I’m not sure I can change any flags for memory management.

Thanks for taking a look at this.

Dennis

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: Thursday, January 21, 2016 11:10 AM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: Paraview (paraview at paraview.org) <paraview at paraview.org>
Subject: [EXT] Re: [Paraview] Linux memory problems exclusive to Paraview

Dennis,

Couple things please.

1) What distribution and version?
2) Can you send use the top couple of lines of top so we know specifically what you are seeing (top output can vary)
3) Second - This is a shot in the dark and you'll have to compile preview to test it. In vtkDataArrayTemplate.cxx - ensure that dontUseRealloc is true. This changes part of the way we manage memory, so it might come into play.

thanks


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, Jan 19, 2016 at 1:23 PM, Dennis Conklin <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
All,

I will never be mistaken for a Linux sys admin, so let me try to tell you what is happening in a hopefully understandable way.

We run Paraview standalone on our workstations – no  remote server, etc.   Just running the executables DL’ed from the website.

We constantly have an issue with Paraview not having enough memory to behave properly.
If I run TOP at the command line, I might see that nothing is using more than 2% of memory, but in the header it says I have 32GB of ram and 28GB is “used” in the terminology of TOP.   This will mean that Paraview will have very little memory available to it (confirmed using Memory inspector) and it will be very slow!     However, other programs, including other post-processors seem to be able to access this “used” memory and perform much better.    What is it about Paraview which makes it unable to utilize this “used” but apparently available memory, while other programs can?

If more info is needed, can someone help me understand how to get the needed info.   After discussing this several times with the sys admins, they just want me to go away because apparently only Paraview has this issue.

Thanks for any help

Dennis

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160121/70ab0769/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: top.png
Type: image/png
Size: 13636 bytes
Desc: top.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160121/70ab0769/attachment.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dist.txt
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160121/70ab0769/attachment.txt>


More information about the ParaView mailing list