Lots of information missing here.<br>1) What are you animating? Single Isovalue for multiple timesteps? Multiple isovalues? <br>2) What data type are you using? Native VTK, Native Ensight, or a 3rd party. Each of the first two give a somewhat unfair advantage to one product, if you're going for a truly even comparison.
<br>3) What data format are you using? Structured, unstructured? 2d, 3d?<br>4) What pipeline/viz tools are you using? <br>5) What exactly are you counting time for? Data load, or just computation? I bet you're just timing the actual time to generate all the isosurfaces, and Ensight gets a big win because it preloads all the data at once where Paraview loads it as it goes.
<br><br><br><div><span class="gmail_quote">On 3/21/06, <b class="gmail_sendername">Terry Jordan</b> <<a href="mailto:tejj@hotmail.com">tejj@hotmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We are running some test of the performance of ensight versus paraview. In<br>the test we use the same data set and create an iso surface (contour). Then<br>we animate the transient data set. We are seeing about 1 order of magnitude
<br>increase in performance over paraview (about 2.5 mins to 29 mins). Does<br>anyone know if ensight is doing something to speed up the performance such<br>as decimation or are their algorithms that much faster?<br><br>
Thanks in advance.<br><br><br>_______________________________________________<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">
http://www.paraview.org/mailman/listinfo/paraview</a><br></blockquote></div><br><br clear="all"><br>-- <br>Randall Hand<br>Visualization Scientist, <br>ERDC-MSRC Vicksburg, MS<br>Homepage: <a href="http://www.yeraze.com">
http://www.yeraze.com</a>