-
Notifications
You must be signed in to change notification settings - Fork 266
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
Improve GUI performance #744
Labels
Comments
adlarkin
added
enhancement
New feature or request
performance
Runtime performance
labels
Apr 6, 2021
Yeah I believe the |
Let's follow up in #556 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Desired behavior
#736 results in good RTF numbers (90-100% on my machine) using TPE in a world of 3000 static shapes when running headless. However, running regular simulation (with the GUI) with the changes in #736 drops RTF to about 30%. There shouldn't be this big of a performance disparity between headless and GUI simulation. I'd like to figure out why using the GUI is causing such a noticeable performance drop.
Alternatives considered
N/A
Implementation suggestion
TBD - I will update this once I can figure out some reasons for the slowdown.
Additional context
None at the moment - I will update this if I find anything else related to this issue that is worth mentioning (could be related to #711).
It looks like the scene broadcaster system doesn't do much if there is no GUI: https:/ignitionrobotics/ign-gazebo/blob/ignition-gazebo5_5.0.0/src/systems/scene_broadcaster/SceneBroadcaster.cc#L255-L257
The text was updated successfully, but these errors were encountered: