Thanks for your reply.<br>I have another question though. You said the two processes communicated via TCP sockets. What do they actually transfer? The final rendered image? The vtk class methods calls? Or both?<br>I also have tested the pvserver on a remote computer, and I connected to the server with 100 M network. I am wondering if the network speed is good enough for paraveiw? In other words, no huge display delay because of network?<br>
Thanks.<br><br>Biao<br><br><div class="gmail_quote">On Mon, Nov 24, 2008 at 11:43 AM, David E DeMarle <span dir="ltr"><<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Mon, Nov 24, 2008 at 1:33 PM, Biao She <<a href="mailto:shebiao@gmail.com">shebiao@gmail.com</a>> wrote:<br>
> Hi all.<br>
> I have tested paraview on a builtin server and a localhost server(run<br>
> pvserver and connect client to it on the same computer). It seems to me that<br>
> the builtin server is much faster than localhost server. Since the computer<br>
> is the same, i am wondering if the localhost server have to readback all the<br>
> data in GPU and transfer these data to client in order to be displayed? On<br>
> the other hand, for the builtin server, the data in GPU is displayed<br>
> directly(no readback). Could you please explain why the localhost is slower<br>
> than builtin?<br>
> Thanks very much!<br>
><br>
> Aaron<br>
><br>
</div></div>> _______________________________________________<br>
> ParaView mailing list<br>
> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
<br>
The builtin server lives inside the same process as the client. All<br>
communication between server and client takes place via pointers and<br>
vtk class methods are directly called.<br>
<br>
"Localhost" ie, running pvserver on the same machine as the client and<br>
connecting to it consists of two separate processes. It is slower<br>
because both processes compete for CPU cycles and memory space more<br>
importantly, because communication between the two takes place via TCP<br>
sockets.<br>
<font color="#888888"><br>
--<br>
David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
28 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: 518-371-3971 x109<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>She, Biao<br>Department of Computing Science,<br>University of Alberta, Edmonton, Canada<br>