[Paraview] [EXTERNAL] D3 filter crash

[Scott, W Alan]

Don’t forget that each pvserver can’t tell that it is sharing the memory with siblings.  Thus, you care about memory use at the node or computer level.

In theory you are correct regarding D3.  It rebalances work, and also creates ghost cells around processor boundaries.  But, it is an old, somewhat moody filter.  Further, it increases memory footprint significantly (at least copies the data).  If you can work without it, do so.  Generally, if you are slow, you need more nodes or less data.  In practice, the D3 filter won’t speed you up.


Alan

From: Quentin d'Avout [mailto:quentin at arrivo-loop.com]
Sent: Wednesday, October 18, 2017 1:04 PM
To: Scott, W Alan <wascott at sandia.gov>; ParaView <paraview at paraview.org>
Subject: RE: [EXTERNAL] [Paraview] D3 filter crash

Hi Alan,

The memory inspector turns back about 1% usage per core, so no overload here.
Running 12 instances on a 16-core machine.
Note: the same case runs fine in serial on the same machine, I’m just trying to speed up the data processing, as well as prove out some scripts I’m building for later use on a cloud machine.

It is my understanding that a D3 filter is required to balance the load across all nodes (working off of recomposed time steps).
Am I getting this wrong?

Quentin d’Avout | Aerodynamics
[Arrivo Loop]<http://www.arrivo-loop.com/>

From: Scott, W Alan [mailto:wascott at sandia.gov<mailto:wascott at sandia.gov>]
Sent: Wednesday, October 18, 2017 11:45 AM
To: Quentin d'Avout <quentin at arrivo-loop.com<mailto:quentin at arrivo-loop.com>>; ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: RE: [EXTERNAL] [Paraview] D3 filter crash

Kill it, that’s ridiculous.

My guess is that you need more nodes?  Before running the D3 filter, try View/ Memory Inspector.  If any nodes are over about 60% or 70%, you either need more resource, or less data.

I’m curious – why are you running the D3 filter?

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Quentin d'Avout
Sent: Wednesday, October 18, 2017 11:50 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] D3 filter crash

Hello all,

I’m able to start a pvserver over multiple cores, connect to it in paraview GUI, open a foam file and load the results.
I then apply a D3 filter before doing anything else, at which point paraview seems to get cranking (window darkens) and pvserver processes show some activity, but nothing else happens.
I let it “run” for a day now, and it is still seemingly applying that filter.
Unfortunately no errors in either terminals (the pvserver and the paraview ones) nor in the paraview GUI output window.

Anybody ever experienced that?
Thank you
Quentin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171018/199988bb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4364 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171018/199988bb/attachment.png>