[Paraview-developers] [EXTERNAL] Re: speed paraview/web

[Scott, W Alan]

I'm pretty sure the issue here is "NoMachine".  For the Kitware folks, this is what I mean when I tell them I am running NX.  There are currently a few ways to remote into an external client computer on your desktop.  I am sure there are others, I am just talking about the ones I know.  The abstract version is that we are running a window into another computer, the remote computer is scraping the pixels off the remote screen, and sending them back to be viewed in our local window.


*         RGS.  With RGS, you log into a remote computer, and "own" the hardware graphics card.  Only one person at a time may be RGS'd into this remote computer (such as a blade in a rack in the back room).  You get hardware acceleration.  The blade or computer you log into can be anything - for instance, I am on a windows box and always log into Linux.

*         NX (NoMachine, nomachine.com) also allows you to log into a remote computer.  It uses a software "graphics rendering card", and for OpenGL, uses Mesa3d.   Since every user that NX's into the remote machine has his own rendering "machine" and framebuffer, numerous, dozens or hundreds of people can NX into a remote machine at a time.  Rendering runs at software speeds - and Mesa3d is horribly slow.  This is the cause of your issues.  As a side issue, if you are running remote server with a big supercomputer as your back end, all the ParaView client sees is images sent to the client - and NX really isn't that slow.

Alan


From: paraview-developers-bounces at paraview.org [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Sebastien Jourdain
Sent: Wednesday, November 06, 2013 10:00 AM
To: kyr
Cc: paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] speed paraview/web

I see two possible reason.
The first one is the binary version of ParaViewWeb 2 is not using your GPU properly while the one you build (PVWeb 1) on that machine does.
The other reason, could be that you are using the latest version of ParaViewWeb 1 which use WebSockets but in a more efficient manner than the current implementation which reduce the latency.
It is currently something that we are aware of and we will tackle once the core framework will be stable enough that we can focus on performance improvement.

Seb

On Wed, Nov 6, 2013 at 9:51 AM, kyr <akyrieleis at gmail.com<mailto:akyrieleis at gmail.com>> wrote:
Hi,

I am using ParaView-Linux-64bit-glibc-2.3.6-NIGHTLY with
JettySessionManager-Server-1.0. With NoMachine I remote log into a machine
with the paraview setup. I display an object in a modified version of the
LiveArticle that came with paraview and using the pv_web_visualizer.py. When
I move the object it is quite slow. In another installation using an earlier
version of Paraview without web socket and without Jetty, the rendering of
the same object is much faster (on the same machine). What could be the
reason ?

Many thanks

k.



--
View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/speed-paraview-web-tp2590.html
Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com.
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20131106/19b0d8bf/attachment-0001.htm>