<div dir="ltr"><div><div><div><div>Dear <span tabindex="-1" id=":1iq.1" style="background:none repeat scroll 0% 0% yellow" class="">Aashish</span>,<br><br></div>Thanks for your reply.<br><br>(1) <br><br>We tried testing it with 2 different data sets of simulation data, one medium sized and one very large:<br></div><br>Medium<br>Cells: 1309489<br>Points: 247984<br>Memory [MB]: 119.179<br>Geometry [MB]: 8.201<br><br>Very Large<br>Cells: 51937191<br>Points: 11019274<br>Memory [MB]: 4709.731<br>Geometry [MB]: 776.237<br><br></div>These <span tabindex="-1" id=":1iq.2" style="background:none repeat scroll 0% 0% yellow" class="">datasets</span> are unstructured grids (tetrahedral meshes) read into <span tabindex="-1" id=":1iq.3" style="background:none repeat scroll 0% 0% yellow" class="">ParaView</span> using the <span tabindex="-1" id=":1iq.4" style="background:none repeat scroll 0% 0% yellow" class="">Phasta</span> data reader.<br><br></div><div>(2) <br><br>The OS used was <span tabindex="-1" id=":1iq.5" style="background:none repeat scroll 0% 0% yellow" class="">Ubuntu</span> <br><br></div><div>(3) <br><br>The graphics card was a <span dir="ltr"><span tabindex="-1" id=":1iq.6" style="background:none repeat scroll 0% 0% yellow" class="">NVIDIA</span> <span tabindex="-1" id=":1iq.7" style="background:none repeat scroll 0% 0% yellow" class="">Quatro</span> K6000 running the <span tabindex="-1" id=":1iq.8" style="background:none repeat scroll 0% 0% yellow" class="">NVIDIA</span> drivers from the <span tabindex="-1" id=":1iq.9" style="background:none repeat scroll 0% 0% yellow" class="">Ubuntu</span> <span tabindex="-1" id=":1iq.10" style="background:none repeat scroll 0% 0% yellow" class="">Repos</span> (v 331.113)</span><br><br></div><div>(4) <br><br>We configured <span tabindex="-1" id=":1iq.11" style="background:none repeat scroll 0% 0% yellow" class="">ParaView</span> using the default <span tabindex="-1" id=":1iq.12" style="background:none repeat scroll 0% 0% yellow" class="">CMake</span> options, changing <span tabindex="-1" id=":1iq.13" style="background:none repeat scroll 0% 0% yellow" class="">VTK</span>_RENDERING_<span tabindex="-1" id=":1iq.14" style="background:none repeat scroll 0% 0% yellow" class="">BACKEND</span>=OpenGL2 and disabling all the plug-ins. These tests were run in serial, as building with <span tabindex="-1" id=":1iq.15" style="background:none repeat scroll 0% 0% yellow" class="">MPI</span> was throwing errors.<br><br></div><div>(5) <br><br>We expected that the OpenGL2 version of <span tabindex="-1" id=":1iq.16" style="background:none repeat scroll 0% 0% yellow" class="">ParaView</span> would be able to volume render faster than the standard <span tabindex="-1" id=":1iq.17" style="background:none repeat scroll 0% 0% yellow" class="">OpenGL</span> version. However the reported frame rates were the same in both builds when clicking and dragging (~2 FPS). <br><br>This is a problem because we're mainly interested in visualising our data and having users able to rotate the model and interact with it. At these frame rates the response is a bit sluggish. <br><br>Also I've done serial test using an OpenGL2 build on Windows using an old GeForce 8800 with the same medium sized data. On this machine the frame rate was similar at around ~1.5 FPS.<br></div><div><br></div><div>(6) <br><br><span tabindex="-1" id=":1iq.20" style="background:none repeat scroll 0% 0% yellow" class="">ParaView</span> was built by checking out the master from git. Sadly I'm not on that test machine now, so I can't <span tabindex="-1" id=":1iq.21" style="background:none repeat scroll 0% 0% yellow" class="">chec</span>k the <span tabindex="-1" id=":1iq.22" style="background:none repeat scroll 0% 0% yellow" class="">SHA</span> <br></div><div><br></div><div>Many thanks for your help again.<br></div><div><br></div><div>Kevin<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 20 March 2015 at 10:33, Aashish Chaudhary <span dir="ltr"><<a href="mailto:aashish.chaudhary@kitware.com" target="_blank">aashish.chaudhary@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey Kevin,<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Mar 19, 2015 at 5:33 PM, Kevin Lau <span dir="ltr"><<a href="mailto:kevin.d.lau@gmail.com" target="_blank">kevin.d.lau@gmail.com</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Dear Aashish,<br><br></div><span class="">Thanks for your reply, I've now managed to build ParaView from the Master branch with VTK_RENDERING_BACKEND set to OpenGL2 and I have noticed a visible difference in the rendering. <br></span></div><span class=""><div><br></div>However comparison of the rendering performance in the interactive mode of builds with the standard OpenGL backend vs the OpenGL2 backend, both show similar frame rates. <br></span></div></div></blockquote><div><br></div><div>Depending on the card and features you are using you may not see a huge bump in performance. On some systems we have seen 300 times performance improvements and on others there were close specially when you have VSync on. Said that, can you provide more infromation on</div><div><br></div><div>1) Data size</div><div>2) OS</div><div>3) Graphics card</div><div>4) Features you have enabled? </div><div>5) You expectation and problem </div><div>6) What SHA of ParaView you are using?</div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Are there other build options that I'm missing? Should I be building the VTK libraries themselves?<br></div></div></blockquote><div><br></div></span><div>Just make sure that you built from a clean state other than that you should be good. </div><div> </div><div>Thanks,</div><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><br><div><div><div>Many thanks,<br><br></div><div>Kevin<div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On 3 March 2015 at 14:53, Aashish Chaudhary <span dir="ltr"><<a href="mailto:aashish.chaudhary@kitware.com" target="_blank">aashish.chaudhary@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Tue, Mar 3, 2015 at 2:43 PM, Kevin Lau <span dir="ltr"><<a href="mailto:kevin.d.lau@gmail.com" target="_blank">kevin.d.lau@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div>Dear Aashish,<br><br></div>Thank you very much for your reply. The latest work you're doing on volume rendering is very impressive.<br></div></div></div></div></blockquote><div><br></div></span><div>Thanks. </div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><br></div><div>In order to access the latest VTK rendering in ParaView would we have to compile both the latest VTK and ParaView from source? Is it possible to link ParaView to specific VTK builds?<br></div></div></div></div></blockquote><div><br></div></span><div>Latest ParaView from source should be fine. Just make sure that you select VTK_RENDERING_BACKEND to OpenGL2 </div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div></div><div><br></div>Also do you know if it is preferential to have a single GPU (i.e. a workstation graphics card) or multiple GPU (i.e. gaming graphics card) when using ParaView?<br></div></div></div></blockquote><div><br></div></span><div>If I remember correctly, we don't explicitly assign tasks to GPU in ParaView if running a single process. You can find more information here: <a href="http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node" target="_blank">http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#Multiple_GPUs_Per_Node</a></div><div><br></div><div>Hope it helps. </div><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div>Many thanks,<br><br></div>Kevin<div><div><br><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 27 February 2015 at 08:15, Aashish Chaudhary <span dir="ltr"><<a href="mailto:aashish.chaudhary@kitware.com" target="_blank">aashish.chaudhary@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear Kevin, <div><br></div><div>First, I would like to mention that we have been working hard to improve rendering in VTK that includes volume rendering as well. You may want to read this source article: <a href="http://www.kitware.com/source/home/post/154" target="_blank">http://www.kitware.com/source/home/post/154</a>. Most of the changes related to this work is now available in VTK github repository in master branch. If you are targetting current VTK, I would suggest that any card that can support OpenGL2.1 or higher would be great. The higher the GPU memory the better. While these newer card will work with the previous version of volume rendering, it may not scale very well (in our testing that's what we have observed). Current the default in ParaView is OpenGL Volume Rendering but that is going to change sometime soon and once that happens you will have OpenGL2 backend for everything. </div><div><br></div><div>Hope this helps. </div><div>- Aashish</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, Feb 26, 2015 at 5:41 PM, Kevin Lau <span dir="ltr"><<a href="mailto:kevin.d.lau@gmail.com" target="_blank">kevin.d.lau@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div><div>Hi, <br><br></div>I'm looking to putting together a workstation to perform realtime volume rendering of our simulation data.<br><br></div><div>Are there any particular GPU features I should look for? <br><br></div><div>If there are multiple GPUs will Paraview be able to take advantage of each GPU for volume rendering?<br><br></div><div>Many thanks<span><font color="#888888"><br><br></font></span></div><span><font color="#888888"><div>Kevin<br></div><div><br></div><br></font></span></div>
<br></div></div>_______________________________________________<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>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" target="_blank">http://markmail.org/search/?q=ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><font face="trebuchet ms, sans-serif"><i>| Aashish Chaudhary <br>| Technical Leader <br>| Kitware Inc. <br></i></font><div><i><font face="trebuchet ms, sans-serif">| </font><a href="http://www.kitware.com/company/team/chaudhary.html" target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div></div></div>
</font></span></div>
</blockquote></div><br></div></div></div></div></div></div>
</blockquote></div></div></div><div><div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><font face="trebuchet ms, sans-serif"><i>| Aashish Chaudhary <br>| Technical Leader <br>| Kitware Inc. <br></i></font><div><i><font face="trebuchet ms, sans-serif">| </font><a href="http://www.kitware.com/company/team/chaudhary.html" target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div></div></div>
</div></div></div></div>
</blockquote></div><br></div></div></div></div></div></div></div>
</blockquote></div></div></div><div><div class="h5"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><font face="trebuchet ms, sans-serif"><i>| Aashish Chaudhary <br>| Technical Leader <br>| Kitware Inc. <br></i></font><div><i><font face="trebuchet ms, sans-serif">| </font><a href="http://www.kitware.com/company/team/chaudhary.html" target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div></div></div>
</div></div></div></div>
</blockquote></div><br></div>