Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to improve Steps/s Speed in SimRobot #77

Open
ItsBean opened this issue Apr 28, 2023 · 1 comment
Open

How to improve Steps/s Speed in SimRobot #77

ItsBean opened this issue Apr 28, 2023 · 1 comment

Comments

@ItsBean
Copy link

ItsBean commented Apr 28, 2023

Dear authors,

I hope this message finds you well. I recently encountered an issue while using SimRobot, specifically related to its slow steps/s performance. When running game.ros2 on SimRobot, I noticed that the calculation speed is limited to approximately 24 steps/s.

However, my system's resource usage appears to be relatively low: the average CPU usage rate is 44.7%, and only 1,495 MB out of 7,708 MB of memory is being utilized. Interestingly, despite having an 8 GB GPU, no programs seem to be loaded into my GPU memory.

I would greatly appreciate any guidance on how to increase the steps/s speed in SimRobot, particularly given my system's available resources. If there are any specific settings or optimizations that could be applied, your recommendations would be invaluable.

Thank you in advance for your assistance, and I look forward to your insights on this matter.

Best regards,

@roefer
Copy link
Contributor

roefer commented Oct 22, 2023

SimRobot is a single-threaded app. Therefore, the physics simulation and the computation of the sensor data are all computed sequentially. The physics library Open Dynamics Engine SimRobot uses has the option to run computations in parallel, but we always experienced random errors when activating this feature, i.e. some values became NaN. And still, camera images would still not be computed in parallel with this option, because they are not computed by that library.

Removing the bottle neck would probably mean a major rewrite of the simulator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants