[Paraview] reading timer log in paraview

[Moreland, Kenneth]

You get a still render every time the render area gets a repaint event.  When I view a data file for the first time, I don't get that many still render entries in the log file.  However, if I drag a window or dialog (like the timer log dialog) over the render area, I get more renders.  So, in short there is probably some window event that is causing ParaView to repaint.

-Ken

________________________________
From: paraview-bounces at paraview.org [mailto:paraview-bounces at paraview.org] On Behalf Of Cally K
Sent: Tuesday, May 13, 2008 11:18 PM
To: ParaView
Subject: [Paraview] reading timer log in paraview

Hi everyone

I would like to know more about reading the timer log in paraview for benchmarking purpose.. I rendered a file with 750,000 points and I received this log

Execute vtkPVGeometryFilter id: 146, 0.156 seconds

Still Render,  0.093 seconds

Still Render,  0.109 seconds



Still Render,  0.094 seconds

Still Render,  0.093 seconds



Still Render,  0.109 seconds

Still Render,  0.109 seconds



Still Render,  0.11 seconds

Still Render,  0.093 seconds



Still Render,  0.094 seconds

Still Render,  0.094 seconds



Still Render,  0.093 seconds





would just like to know..

why is there so many still render.. and I know I am reading it wrong.. where can I find extra information about reading the log. or any other benchmarking ways





..sorry I know its a basic thing.. but could someone help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20080514/c3b27d19/attachment-0001.htm>