[Paraview] Client-server mode / data streaming problem
Pierre-Olivier Dallaire
pierre-olivier.dallaire at videotron.ca
Tue Jan 5 11:10:42 EST 2010
Perfect, works now, thanks !
On 2010-01-05, at 10:36 AM, Utkarsh Ayachit wrote:
> That was a nasty one! Thanks for reporting it. I've committed a fix
> for this bug.
>
> /cvsroot/ParaView3/ParaView3/Servers/ServerManager/Resources/rendering.xml,v
> <-- Servers/ServerManager/Resources/rendering.xml
> new revision: 1.382; previous revision: 1.381
> /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMUnstructuredDataParallelStrategy.cxx,v
> <-- Servers/ServerManager/vtkSMUnstructuredDataParallelStrategy.cxx
> new revision: 1.5; previous revision: 1.4
>
> Utkarsh
>
> On Mon, Jan 4, 2010 at 3:58 PM, Pierre-Olivier Dallaire
> <pierre-olivier.dallaire at videotron.ca> wrote:
>> Here is what I get from this test :
>>
>> Local Process
>> Still Render, 0.057886 seconds
>> Execute vtkPolyDataMapper id: 413, 1.6e-05 seconds
>> Still Render, 0.070324 seconds
>> Execute vtkPolyDataMapper id: 413, 1.8e-05 seconds
>> Still Render, 0.045106 seconds
>> Execute vtkPolyDataMapper id: 413, 2.1e-05 seconds
>> Still Render, 0.038055 seconds
>> Execute vtkPolyDataMapper id: 413, 2e-05 seconds
>> Interactive Render, 42.5521 seconds
>> Execute vtkMPIMoveData id: 621, 39.9256 seconds
>> Execute vtkMPIMoveData id: 624, 2.30231 seconds
>> Execute vtkPolyDataMapper id: 410, 3.5e-05 seconds
>> Execute vtkPolyDataMapper id: 410, 1.4e-05 seconds
>> Interactive Render, 0.002586 seconds
>> Execute vtkPolyDataMapper id: 410, 2.4e-05 seconds
>> Interactive Render, 0.001532 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001864 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001908 seconds
>> Execute vtkPolyDataMapper id: 410, 2.2e-05 seconds
>> Interactive Render, 0.001933 seconds
>> Execute vtkPolyDataMapper id: 410, 2.1e-05 seconds
>> Interactive Render, 0.001626 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.001455 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.00338 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.001561 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001537 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.001489 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.001558 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001595 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001546 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001454 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001633 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Interactive Render, 0.001517 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001516 seconds
>> Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds
>> Interactive Render, 0.001481 seconds
>> Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds
>> Still Render, 33.0572 seconds
>> Execute vtkMPIMoveData id: 621, 32.6987 seconds
>> Execute vtkPolyDataMapper id: 413, 3e-05 seconds
>> Execute vtkPolyDataMapper id: 413, 2.4e-05 seconds
>>
>>
>>
>> Server
>> Execute vtkQuadricClustering id: 633, 0.125393 seconds
>> Execute vtkMPIMoveData id: 621, 39.3476 seconds
>> Dataserver sending to client, 39.3474 seconds
>> Execute vtkOrderedCompositeDistributor , 7.5e-05 seconds
>> Execute vtkMPIMoveData id: 624, 1.88785 seconds
>> Dataserver sending to client, 1.88762 seconds
>> Execute vtkOrderedCompositeDistributor , 7e-05 seconds
>> Execute vtkMPIMoveData id: 621, 32.217 seconds
>> Dataserver sending to client, 32.2167 seconds
>> Execute vtkOrderedCompositeDistributor , 7.7e-05 seconds
>>
>> On 2010-01-04, at 3:47 PM, Utkarsh Ayachit wrote:
>>
>>> Try this:
>>> * Open Tools | Timer Log.
>>> * Change the "Time Threshold" to "Show All"
>>> * Pan etc. then click "Refresh"
>>> If there are any entires in there that say "vtkMPIMoveData" it
>>> represents a data delivery to the client.
>>> * I can see data-delivery happens when I change properties on the
>>> source, but never when merely interacting with it.
>>>
>>> Utkarsh
>>>
>>>
>>> On Mon, Jan 4, 2010 at 3:39 PM, Pierre-Olivier Dallaire
>>> <pierre-olivier.dallaire at videotron.ca> wrote:
>>>> Hi !
>>>>
>>>> yes, I'm connecting to a server machine which is running pvserver. The local and server machines have exactly
>>>> the same cvs version.
>>>>
>>>> I tried different cases / an easy one was to open an stl file located on the server machine side. I'm monitoring the network
>>>> traffic on the client machine. As soon as I try to move/rotate the stl geometry, I can see that the download traffic is going up
>>>> and reach the maximum for some time.
>>>>
>>>> Thanks
>>>>
>>>> PO
>>>>
>>>>
>>>> On 2010-01-04, at 3:33 PM, Utkarsh Ayachit wrote:
>>>>
>>>>> So, if I understand correctly, you are using local-rendering mode i.e.
>>>>> deliver data to client and render. How are you determining that the
>>>>> client is re-downloading the data? I just tried with a simple sphere
>>>>> source, and could not reproduce the behavior.
>>>>>
>>>>> Utkarsh
>>>>>
>>>>> On Mon, Jan 4, 2010 at 2:22 PM, Pierre-Olivier Dallaire
>>>>> <pierre-olivier.dallaire at videotron.ca> wrote:
>>>>>> Good afternoon,
>>>>>>
>>>>>> using the latest cvs version, it seems that the client-server mode does not work as well as before (early december).
>>>>>> For some reason, every time I try to pan or rotate, the client application re-downloads all the data, which was not the case before.
>>>>>> Using the standard view buttons work properly doe not generate a full re-download of the data. With this new behaviour, it's impossible
>>>>>> to work under the client-server mode.
>>>>>>
>>>>>> Suggestions ?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> PO
>>>>>> _______________________________________________
>>>>>> Powered by 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
>>>>>>
>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>
>>>>
>>>>
>>
>>
More information about the ParaView
mailing list