V3.2.3 Taking longer to render
Posted: 28 Nov 2015, 15:32
Hi,
After updating VREP to version 3.2.3 (PRO EDU) I have noticed a lower performance in rendering, comparing to version 3.2.2.
Up to version 3.2.2, the rendering of the scene in my computer was taking 8 to 10ms.
With version 3.2.3, the rendering is consuming 30ms.
These values are the ones that appear in app title.
This happens in the same computer, with same scene.
Additional info:
For the simulation I am working with, I need to work with real-time mode enabled.
With 3.2.2 version:
the dynamics calculations passes (10) are taking 30ms to run,
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms). I have threads for processing UI, from time to time it shows 1ms.
simulation time does not lags behind real-time (it sometimes does lags a bit, but vrep can quickly catch up).
Enabling threaded rendering I got same behavior
With version 3.2.3
the dynamics calculations passes (10) are taking 30ms to run (OK)
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms). I have threads for processing UI, from time to time it shows 1ms.
simulation time LAGS behind real-time. In 60s simulation, it lags 15s.
Enabling threaded rendering, I got the oscilation information in Information TExt:
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms).
or
Scripts executed: Non threaded 13 (64ms), running threads: 0 (31ms).
cannot tell for sure the values (they change very quickly), but are about those
Simulation also lags behind real-time 15s in 60s running.
Is the running threads time taking into account the rendering time?
Why does it seems that nonthreaded time is being affect by rendering?
Does while rendering the objects are being locked for read and thus simulation is stalled? (but now the information is shown and previously was not?)
Note
OS: Windows 10 Pro, x64.
Thanks,
Tiago
After updating VREP to version 3.2.3 (PRO EDU) I have noticed a lower performance in rendering, comparing to version 3.2.2.
Up to version 3.2.2, the rendering of the scene in my computer was taking 8 to 10ms.
With version 3.2.3, the rendering is consuming 30ms.
These values are the ones that appear in app title.
This happens in the same computer, with same scene.
Additional info:
For the simulation I am working with, I need to work with real-time mode enabled.
With 3.2.2 version:
the dynamics calculations passes (10) are taking 30ms to run,
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms). I have threads for processing UI, from time to time it shows 1ms.
simulation time does not lags behind real-time (it sometimes does lags a bit, but vrep can quickly catch up).
Enabling threaded rendering I got same behavior
With version 3.2.3
the dynamics calculations passes (10) are taking 30ms to run (OK)
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms). I have threads for processing UI, from time to time it shows 1ms.
simulation time LAGS behind real-time. In 60s simulation, it lags 15s.
Enabling threaded rendering, I got the oscilation information in Information TExt:
Scripts executed: Non threaded 13 (34ms), running threads: 0 (0ms).
or
Scripts executed: Non threaded 13 (64ms), running threads: 0 (31ms).
cannot tell for sure the values (they change very quickly), but are about those
Simulation also lags behind real-time 15s in 60s running.
Is the running threads time taking into account the rendering time?
Why does it seems that nonthreaded time is being affect by rendering?
Does while rendering the objects are being locked for read and thus simulation is stalled? (but now the information is shown and previously was not?)
Note
OS: Windows 10 Pro, x64.
Thanks,
Tiago