[Paraview] memory load on client when running on server
Burlen Loring
bloring at lbl.gov
Thu Jun 19 15:40:03 EDT 2014
Ug. you're using the multicore option to start the servers! I believe
that this forces remote rendering off. That would explain your issues.
Could you try duisabling the multi core option and start your servers
manually?
On 06/19/2014 12:29 PM, Burlen Loring wrote:
> OK, one possibility is that it may be related to remote rendering
> settings. Under menu Edit->Settings->Render View->Server there is a
> remote render threshold. I always set this to 0 bytes to ensure remote
> parallel rendering. What's yours set to?
>
> On 06/19/2014 12:18 PM, jean mensa wrote:
>> Sorry, I didn't explain it properly. I have already tried to connect
>> to a pvserver from a GUI running on the client (without an ssh
>> connection then) but it also drains the memory on Xorg. What is the
>> load supposed to be on a client-pvserver connection?
>> Thanks,
>>
>>
>> On Thu, Jun 19, 2014 at 3:08 PM, Burlen Loring <bloring at lbl.gov
>> <mailto:bloring at lbl.gov>> wrote:
>>
>> Jean,
>>
>> What you describe is expected. X forwarding doesn't work well for
>> visualizing large datasets. The point is : don't use X
>> forwarding. The links show how to configure the client server
>> connection without X forwarding. Make sure that there is no -X on
>> the ssh command line.
>>
>> Burlen
>>
>>
>> On 06/19/2014 11:46 AM, jean mensa wrote:
>>> When I do that Xorg process on the client drains the memory up
>>> until it crashes. The connection I think is properly established
>>> since it works fine for smaller datasets. What should the load
>>> on the client be in that case?
>>> j
>>>
>>>
>>> On Thu, Jun 19, 2014 at 2:14 PM, Burlen Loring <bloring at lbl.gov
>>> <mailto:bloring at lbl.gov>> wrote:
>>>
>>> Yes, this is expected. The OpenGL calls get piped to your
>>> local system. This includes data like vertices and colors as
>>> well. X forwarding doesn't give good performance and with
>>> large data it may not even be feasible.
>>>
>>> You need to set up client server connection.
>>>
>>> http://www.paraview.org/Wiki/Reverse_connection_and_port_forwarding
>>> http://www.paraview.org/Wiki/ParaView:Server_Configuration
>>> http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server
>>> http://www.paraview.org/Wiki/ParaView_And_Mesa_3D
>>>
>>>
>>>
>>>
>>> On 06/19/2014 10:33 AM, jean mensa wrote:
>>>> Hi all,
>>>> I have a rather large unstructured pvtu dataset (about 4
>>>> million points) which I am visualizing on a remote server.
>>>> I am running the paraview GUI (with the multicore option)
>>>> on the server and I connect to it via ssh sharing the X
>>>> server. In this way I can control the GUI running on the
>>>> serve. I thought that with this configuration I would only
>>>> receive a screenshot of the window and no actual data from
>>>> paraview but the client seems to share at least some of the
>>>> load of the visualization. Is this the expected behaviour?
>>>> How can I avoid loading data on the client side?
>>>> Thanks in advance,
>>>>
>>>> --
>>>> *Jean A. Mensa*
>>>> /Graduate Assistant/
>>>> University of Miami
>>>> RSMAS - MPO
>>>> 4600 Rickenbacker Causeway
>>>> Miami, FL 33149-1098
>>>>
>>>>
>>>> _______________________________________________
>>>> Powered bywww.kitware.com <http://www.kitware.com>
>>>>
>>>> Visit other Kitware open-source projects athttp://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://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>>
>>>
>>> --
>>> *Jean A. Mensa*
>>> /Graduate Assistant/
>>> University of Miami
>>> RSMAS - MPO
>>> 4600 Rickenbacker Causeway
>>> Miami, FL 33149-1098
>>
>>
>>
>>
>> --
>> *Jean A. Mensa*
>> /Graduate Assistant/
>> University of Miami
>> RSMAS - MPO
>> 4600 Rickenbacker Causeway
>> Miami, FL 33149-1098
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140619/77d1693e/attachment.html>
More information about the ParaView
mailing list