One way of pinpointing the bottleneck is to look at Window -> Timer Log. I am guessing IO is the problem here. However, clip filter might be also taking a long time with 4.5 million cells on 1 processor. I recommend switching to at least binary. A
4.5 Gb ascii file is ridiculous. A format that supports compression like the VTK-XML formats might also help. Also, are you using the cut or clip filter? <br><br>-berk<br><br><div><span class="gmail_quote">On 10/16/06, <b class="gmail_sendername">
Alberto Fernandez</b> <<a href="mailto:alberto@cognitdesign.com">alberto@cognitdesign.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;">
Even for a simple solid rendering. I'm trying to open a case with 4.5<br>million and its been working for 6 hours now. Is it normal to have that<br>kind of performance if the data is in ascii? Granted the geo file is big<br>
(4Gb) but I thought it could be handled.<br>I'm going to check out HAVS. Thanks for the suggestion.<br><br>Claudio Silva escribió:<br>> What kind of rendering are you doing?<br>><br>> For volume rendering (and isosurface generation), HAVS can render up
<br>> to 6 million tets/sec on the latest graphics hardware (single machine).<br>><br>> HAVS has recently been added to Paraview, and is also available stand<br>> alone:<br>><br>> <a href="http://havs.sourceforge.net">
havs.sourceforge.net</a><br>><br>><br>> On Oct 15, 2006, at 11:06 AM, Alberto Fernandez wrote:<br>><br>>> I have a question regarding paraview performance. I'm using paraview<br>>> to visualize CFD results. The results are written in ensight format
<br>>> as ascii. I have been doing some work on a model with a unstructured<br>>> mesh of about 1.5 million cells. Using simply a clip filter cutting<br>>> with a scalar takes a lot of time. It is not big for just a frame but
<br>>> we are calculating 20 time steps. If we want to calculate that<br>>> cliping (to find a free surface) to create an animation it takes<br>>> about 15 or 20 minutes. The machine is an AMD athlon with 4 GB.
<br>>> We are interested in processing a calculation with around 5 million<br>>> cells. We have tried and it takes hours.<br>>> Is there a way of improving this performance through some settings or<br>>> similar?
<br>>> Does having the results written in ascii (it takes quite some room)<br>>> have some effect on performance?<br>>><br>>> --Alberto Fernández<br>>> <a href="mailto:alberto@cognitdesign.com">
alberto@cognitdesign.com</a><br>>><br>>> Cognit Design<br>>> C/Arquitecte Sert, 31 Local 3 Vila Olímpica<br>>> 08005 Barcelona<br>>> Telf: 93 532 29 94<br>>> Fax: 93 531 59 42<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>><br><br>--<br>Alberto Fernández<br><a href="mailto:alberto@cognitdesign.com">alberto@cognitdesign.com</a><br><br>Cognit Design<br>C/Arquitecte Sert, 31 Local 3<br>
Vila Olímpica<br>08005 Barcelona<br>Telf: 93 532 29 94<br>Fax: 93 531 59 42<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>