Gazebo Answers logo

We are working according: Tutorial on thread-island and with the repositories suggested by Ying Lu as answered to: this question

Our goal is to reach real time factor of 1 in our simulation.

We have the following computer:

HP EliteDesk 800 G3 TWR (Y1B39AV)
16GiB System Memory                                                                                   Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (x8)

And the following graphical card: GeForce GTX 1080

We are originally interested with running our simulation with two island_threads.

We checked the following 3 configurations:

  1. gazebo --verbose -o unthrottled0 gazebo/worlds/dual_pr2.world
  2. gazebo --verbose -o unthrottled1 gazebo/worlds/dual_pr2.world
  3. gazebo --verbose -o unthrottled2 gazebo/worlds/dual_pr2.world

To our surprise:

  1. unthrottled 0 ==> Real Time factor is around 0.95
  2. unthrottled 1 ==> Real Time factor is around 0.41 !!!!!!
  3. unthrottled 2 ==> Real Time factor is around 0.62 !!!!!!

To be honest, with a much less good computer we got good results regarding real time factor (from 0.60 without to 0.75 with 2 islands) so we had a lot of expectations toward the strong station.

I am attaching a screen capture of gazebo with a filtered htop.

Obviously, we are doing something wrong.... Do you have an idea?

Thanks a lot

Originally posted by mhallak on Gazebo Answers with karma: 96 on 2017-11-07

Post score: 0


1 Answer 1


Gazebo Answers logo

The solution of the problem is to compile gazebo with the flag release.

./src/catkin/bin/catkin_make_isolated -DCMAKE_BUILD_TYPE=RELEASE

Then the real time factor is as expected.

The default compile flag is RelWithDebInfo and it seems that running gzserver compiled with debug flag is catastrophic for the real time factor....

Originally posted by mhallak with karma: 96 on 2017-12-06

This answer was ACCEPTED on the original site

Post score: 1


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.