Hi Robert,
> 1) might be the OS or other application/process running at the same time
> and periodically running,, make sure you
> have as few other apps and processes running during testing
> 2) the OpenGL fifo might be very close to filling on each frame and
> sometimes fills complete
Hi Daniel,
On Wednesday, 23 June 2021 at 15:32:47 UTC+1 daniel.t...@gmail.com wrote:
> the 200ms seem to be very rare spikes and the median draw time for an
> animation step for the bigger model is 40ms and for the smaller model
> 13ms.
>
The spike could be an indication of a couple of
Hi Robert,
the 200ms seem to be very rare spikes and the median draw time for an
animation step for the bigger model is 40ms and for the smaller model 13ms.
> How much dynamic data needs to be transferred when it's updated?
The bigger model has 110MB of coordinates and normals to be
Hi Daniel,
With the details provided it's not possible to know exactly what is causing
the bottleneck in your case, it may be connected to transfer of data, but
200ms is a big stall so it may be something else going wrong than just the
data transfer across the bus.
How much of your scene
