[Paraview] Not clear about paraview's benchmark

[David E DeMarle]

Hello,

vtkPVUpdateSuppressor's main purpose is to break the visualization
pipeline into segments across processors. It suppresses vtk's pipeline
update mechanism on segments that don't have a full path upstream to
the data.  Instead, each processor's pipeline ends with a PVUS, and
the client calls their ForceUpdate methods synchronously to make it
all function as an unbroken pipeline would.

vtkOrderedCompositeDistributor is inserted into the Render Server's
pipeline. When transparency is used, it shuffles the data pieces
around so that they are rendered in back to front order.

cheers,
Dave DeMarle


On Mon, May 19, 2008 at 12:25 AM, Cally K <kalpana0611 at gmail.com> wrote:
> Hi everyone, I have run my polydata file on Paraview, and attached is
> the result I obtained from the timer log. I was wondering if someone
> could explain the results, as I only understand partially. From what I
> understand,the images are being sent back to the local machine for
> rendering..and the processing happens at the servers.. am I right...
> what does vtkPVUpdateSuppressor and ordered
> vtkOrderedCompositeDistributor do..?
>
> Thanks...
>
>
> Local Process
> Execute vtkMPIMoveData id: 296,  6.47037 seconds
> Still Render,  16.0107 seconds
>
>
>
>
> Server, Process 0
> Execute vtkXMLPolyDataReader id: 183,  0.616797 seconds
> Execute vtkPVGeometryFilter id: 208,  0.091801 seconds
> Execute vtkMPIMoveData id: 296,  5.6583 seconds
>    Dataserver gathering to 0,  2.7758 seconds
>    Dataserver sending to client,  2.8819 seconds
> Execute vtkPVUpdateSuppressor id: 311,  7.7e-05 seconds
> Execute vtkOrderedCompositeDistributor ,  6.5e-05 seconds
>
>
> Server, Process 1
> Execute vtkXMLPolyDataReader id: 183,  6.6e-05 seconds
> Execute vtkPVGeometryFilter id: 208,  0.133452 seconds
> Execute vtkMPIMoveData id: 296,  0.629643 seconds
>    Dataserver gathering to 0,  0.629556 seconds
> Execute vtkPVUpdateSuppressor id: 311,  3.5e-05 seconds
> Execute vtkOrderedCompositeDistributor ,  3.1e-05 seconds
>
>
> Server, Process 2
> Execute vtkXMLPolyDataReader id: 183,  7.7e-05 seconds
> Execute vtkPVGeometryFilter id: 208,  0.004583 seconds
> Execute vtkMPIMoveData id: 296,  1.03612 seconds
>    Dataserver gathering to 0,  1.03605 seconds
> Execute vtkPVUpdateSuppressor id: 311,  3.5e-05 seconds
> Execute vtkOrderedCompositeDistributor ,  3e-05 seconds
>
>
> Server, Process 3
> Execute vtkXMLPolyDataReader id: 183,  0.000124 seconds
> Execute vtkPVGeometryFilter id: 208,  0.137474 seconds
> Execute vtkMPIMoveData id: 296,  1.28697 seconds
>    Dataserver gathering to 0,  1.28688 seconds
> Execute vtkPVUpdateSuppressor id: 311,  3.5e-05 seconds
> Execute vtkOrderedCompositeDistributor ,  3e-05 seconds
>
>
> Server, Process 4
> Execute vtkXMLPolyDataReader id: 183,  0.00012 seconds
> Execute vtkPVGeometryFilter id: 208,  0.189505 seconds
> Execute vtkMPIMoveData id: 296,  1.61418 seconds
>    Dataserver gathering to 0,  1.61409 seconds
> Execute vtkPVUpdateSuppressor id: 311,  3.6e-05 seconds
> Execute vtkOrderedCompositeDistributor ,  3.1e-05 seconds
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>