[Paraview-developers] How does ParaView schedule render tasks among all the processes?

[Biddiscombe, John A.]

Jie


1)      each reader/source must split pieces itself. If I am a vtkSTUFFreader, when I execute, I am given a piece number or an extent (depending on datatype), based on this information, I read the part of the data that I was told to (the reader has to work out how to get the piece it was asked for)

2)      The number of pieces is currently always the same as the number of MPI ranks (but it doesn’t have to be). A reader can set MAX_PIECES to -1 initially before the description in 1) above happens, which tells the pipeline that it is allowed to split the data into as many pieces as it wants. Be careful that the pipeline also uses pieces to represent streaming data pieces, which is confusing, I am not considering this case here. data paralle pieces are not quite the same as streaming pieces. we’re talking data parallel now.

3)      assignment of piece number is essentially MPI rank
Hope this helps

JB

From: paraview-developers-bounces at paraview.org [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Jie Chen
Sent: 14 February 2012 17:38
To: paraview-developers at paraview.org
Subject: [Paraview-developers] How does ParaView schedule render tasks among all the processes?


Hi all,

I have installed the ParaView-3.12.0 on a cluster with MPI enabled. And I use it in a client-server mode.(pvserver is running on the cluster)

I'm curious about how ParaView process a task parallelly. The following is my questions:
(1) How does ParaView split a file into multi-pieces for parallel processing, and how to combine the results together?  Is there any special process which handles these splitting and combining works?

(2) What policy does ParaView use when it computes the number of pieces?

(3)What policy does ParaView use when it assign the pieces to all the processes?

I'm just beginning to look into the ParaView source code. Hope somebody can give me some clue.

Thanks

Jie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20120214/81bc9003/attachment.htm>