<div dir="ltr">Hi Den,<div><br></div><div>thanks for your interesting feedback.</div><div><br></div><div>Regarding your first point, I don't know how to tune the delivery option for pvserver from the python side, but looking at the C++ code should not be too difficult to figure out what need to be done.</div>
<div><br></div><div>For the second point, you are right, it seems that ParaViewWeb induce a double render call, one in interactive mode and another one for the image sent to the client as a full resolution render. And it is likely that it affect the performances. </div>
<div><br></div><div>If those points are critical for you, we can certainly help via a support contract to integrate some fix faster into the current code base.</div><div><br></div><div>Thanks again for your feedback,</div>
<div><br></div><div>Seb</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 8, 2014 at 10:55 PM, Den Fairol <span dir="ltr"><<a href="mailto:den.fairol@infovalley.net.my" target="_blank">den.fairol@infovalley.net.my</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Sorry for the hiatus. To hastily feed on Seb’s curiosity, yes indeed the behavior is blind to data source type. As for Aashish’s concern, it is a misunderstanding. I did mention I ran the client on VM, not the pvserver. Thus discounting hardware as the root cause. Actually I just realized that the 26 FPS was from the standalone ParaView (i.e. not connected to pvserver as can be seen in the pipeline browser). Upon connecting to a local pvserver, the FPS plummeted quite dramatically. Adjusting it to ‘shared memory/localhost’ does the trick (more info here: </span><a href="http://paraview.org/Wiki/ParaView/Image_Compressor_Configuration" target="_blank">http://paraview.org/Wiki/ParaView/Image_Compressor_Configuration</a>)<span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">. The obvious question would be, how can we do that in ParaViewWeb?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">A second rather counter-intuitive question, why couldn’t we see a degraded image in ParaViewWeb when interacting with a polygonal object, it only appears so in the VTK render window (first image is without interaction, second is with interaction)? This observation does not reflected in ParaView (i.e. you’ll see the lost in quality during interaction). Ultimately how much of this behavior (if any) impact the overall performance?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Den<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><img border="0" width="780" height="519" src="cid:image002.png@01CF0D42.697AC590"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><img border="0" width="780" height="518" src="cid:image003.png@01CF0D42.697AC590"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><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""> Aashish Chaudhary <a href="mailto:[mailto:aashish.chaudhary@kitware.com]" target="_blank">[mailto:aashish.chaudhary@kitware.com]</a> <br>
<b>Sent:</b> 30 November 2013 4:56 AM<br><b>To:</b> Sebastien Jourdain<br><b>Cc:</b> Den Fairol; <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br><b>Subject:</b> Re: [Paraview] ParaViewWeb rendering performance<u></u><u></u></span></p>
<div class="im"><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">If you are using VM or offscreen rendering, then it is likely that you are not using hardware acceleration (depending on your setup, VM tool, and hardware). A simple check using glxgears could give your more info. <u></u><u></u></p>
<div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">- Aashish<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">
<u></u> <u></u></p><div><div class="im"><p class="MsoNormal">On Fri, Nov 29, 2013 at 11:38 AM, Sebastien Jourdain <<a href="mailto:sebastien.jourdain@kitware.com" target="_blank">sebastien.jourdain@kitware.com</a>> wrote:<u></u><u></u></p>
<div><p class="MsoNormal">Hi Den,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">out of curiosity, does basic surface rendering with sample VTK dataset work as slow? In other word, is it just the volume rendering that does not behave the same?<u></u><u></u></p>
</div><div><p class="MsoNormal">I'm surprised to see a so huge difference in term of performance. <u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Seb<u></u><u></u></p>
</div></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><div class="im"><div><div><p class="MsoNormal">On Fri, Nov 29, 2013 at 1:38 AM, Den Fairol <<a href="mailto:den.fairol@infovalley.net.my" target="_blank">den.fairol@infovalley.net.my</a>> wrote:<u></u><u></u></p>
</div></div></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt"><div class="im"><div><div><div><div><p class="MsoNormal">
Hi,<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">How can I improve the surface rendering performance of ParaViewWeb (besides tweaking the still/interactive-image quality settings)? I could get a decent FPS (26+/-) on ParaView (as depicted below) and ~50% decrease is naturally expected when ported to ParaViewWeb (based on volume rendering of some voxels). Unfortunately, the performance drop is much more critical than initially presumed as I could barely scoop out 1 FPS. Do note that both client and server are executed locally (i.e. if I launched the client through a VM or remotely, then the low FPS will be further aggravated). The dataset specifications are included at the bottom.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________</p><div class="im"><br>Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br><br>Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>Follow this link to subscribe/unsubscribe:<br><a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><u></u><u></u></div><p></p></blockquote></div>
<p class="MsoNormal"><u></u> <u></u></p></div><div class="im"><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br><br>Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>Follow this link to subscribe/unsubscribe:<br><a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><u></u><u></u></p></div></div><div class="im">
<p class="MsoNormal"><br><br clear="all"><u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">-- <br>| Aashish Chaudhary <br>| R&D Engineer <br>| Kitware Inc. <br>
| <a href="http://www.kitware.com" target="_blank">www.kitware.com</a> <u></u><u></u></p></div></div></div></div></blockquote></div><br></div>