<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1181436831;
mso-list-type:hybrid;
mso-list-template-ids:1704214264 -1693816178 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Alan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> paraview-developers-bounces@paraview.org [mailto:paraview-developers-bounces@paraview.org]
<b>On Behalf Of </b>Sebastien Jourdain<br>
<b>Sent:</b> Wednesday, November 06, 2013 10:00 AM<br>
<b>To:</b> kyr<br>
<b>Cc:</b> paraview-developers@paraview.org<br>
<b>Subject:</b> [EXTERNAL] Re: [Paraview-developers] speed paraview/web<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">I see two possible reason.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Seb<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Wed, Nov 6, 2013 at 9:51 AM, kyr <<a href="mailto:akyrieleis@gmail.com" target="_blank">akyrieleis@gmail.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Hi,<br>
<br>
I am using ParaView-Linux-64bit-glibc-2.3.6-NIGHTLY with<br>
JettySessionManager-Server-1.0. With NoMachine I remote log into a machine<br>
with the paraview setup. I display an object in a modified version of the<br>
LiveArticle that came with paraview and using the pv_web_visualizer.py. When<br>
I move the object it is quite slow. In another installation using an earlier<br>
version of Paraview without web socket and without Jetty, the rendering of<br>
the same object is much faster (on the same machine). What could be the<br>
reason ?<br>
<br>
Many thanks<br>
<br>
k.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/speed-paraview-web-tp2590.html" target="_blank">
http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/speed-paraview-web-tp2590.html</a><br>
Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</body>
</html>