[Paraview] How to interpret timer log

[chew ping]

Hi all,

 

I'm doing parallel rendering using 1 client (dual core laptop) and 2 cluster servers (dual core desktop)

below is the timer log result i collected when i run: mpirun -np 4 pvserver

 

-----------------------------------------------------------------------------------------------

Local Process

Still Render, 3.029 seconds

Execute vtkMPIMoveData id: 457, 1.98248 seconds

 

 

Server, Process 0

Execute vtkFileSeriesReader id: 176, 0.637821 seconds

Execute vtkMPIMoveData id: 457, 1.49186 seconds

Dataserver gathering to 0, 0.829525 seconds

Dataserver sending to client, 0.661658 seconds

 

Server, Process 1

Execute vtkMPIMoveData id: 457, 0.141821 seconds

Dataserver gathering to 0, 0.141544 seconds

 

Server, Process 2

Execute vtkMPIMoveData id: 457, 0.243584 seconds

Dataserver gathering to 0, 0.243318 seconds

 

Server, Process 3

Execute vtkMPIMoveData id: 457, 0.191589 seconds

Dataserver gathering to 0, 0.191303 seconds

 

-----------------------------------------------------------------------------------------------------

 

i have difficulty interpreting the timer log, my guess is:

 

Scenario 1: 

Process 0 reads the whole data, disseminate the dats into 4 pieces, then distribute to itself and Process 1&2&3,

each node will process the data and send it back Process 0,

Process 0 gather all data and send it back to client,

client renders the data

 

Scenario 2:

Process 0 reads the whole data, distribute the whole data to Process 0&1&2&3,

each node will 'take' their own piece of data to process, then send it back Process 0,

Process 0 gather all data and send it back to client,

client renders the data

   

Which scenario is the correct one? or both are wrong?

 

is there any resources i could refer to find what does it mean by: Execute vtkFileSeriesReader, Execute vtkMPIMoveData?

 

any help / feedback is highly appreciated!

thanks!

 

regards,

chewping

 

 

 

 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20090925/5f8a3002/attachment-0001.htm>