Frame rate number needs improvement

[jaswantp (Jaswant Panchumarti)]

I’m rendering volumes in a paraview client (macos). The data lives on a different machine running pvserver. I notice that Paraview uses remote rendering all the time for even small volumes and there’s no way to override this. This is not interactive at all, even on a really good connection. I wanted to check the fps but the values it shows do not make sense.

If you turn on the “Show Annotation” checkbox in ParaView Settings → Render View, the value shown for the “Frame rate (approx): … fps” is unrealistic. It shows numbers in the range 2400-2600, but that’s not true.

In the screen-recording below, only the orientation axes is drawn. vtkRenderWindow::Render() takes 0.4ms so 1000/0.4 ~ 2500 is where it got that number from.

I believe the label is incorrect, and should be called render throughput. A frame rate should take into account display refresh, qt blits.

[mwestphal (Mathieu Westphal (Kitware))]

@jaswantp

notice that Paraview uses remote rendering all the time for even small volumes and there’s no way to override this.

Remote Render Threshold

[jaswantp (Jaswant Panchumarti)]

Remote Render Threshold

As I’ve said in my post, there’s no way to override it, atleast in 6.2.0. What I’m noticing is that setting has no effect when a volume representation is shown in the render view.

I’ve set it to 1024000 (~1TB) and even for a small 35 KB volume, it still does remote rendering!

[mwestphal (Mathieu Westphal (Kitware))]

@jaswantp

I’ve set it to 1024000 (~1TB) and even for a small 35 KB volume, it still does remote rendering!

Ha! thats a bug then.

[GregVernon]

I can confirm that I’ve felt this same behavior but had just chalked it up to “must just be some inherent limitation in remote-local mode” and so had accepted it as the status quo. So thanks @jaswantp for reporting this!