Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Gazebo Real Time Factor going down

asked 2020-05-19 03:59:04 -0600

manderino
11 ●1 ●1 ●2

Hi, I have a problem with the use of Gazebo I'm running an autonomous car simulator into gazebo and another node that I made for ground removal of the lidar sensor

When I run this node the real time factor of gazebo is dropping down to 0.3 from 1. I understand that this could be because of the load on the CPU but the fact is that none of the CPU cores is on full load and the global cpu utilization is around 20%, I can run other more heavy processes without bringing it down.

Is there a way to keep this up or force the real time factor to 1?

Thank you

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-06-09 17:45:04 -0600

Weasfas
1695 ●12 ●91 ●41

updated 2020-06-09 17:45:53 -0600

Hi @manderino,

The main problem is not (almost) Gazebo but the bottleneck generated by the pointclouds generation. I am sure you are using a ray plugin instead of a gpu_ray. The ray plugin is forcing Gazebo to generate the pointclouds with the CPU and that is a very slow tasks.

Change the Gazebo plugin to use a gpu_ray and you will maintaint the real time factor near 1.

The velodyne_simulator package contains an implementation of a gpu_ray lidar plugin.

edit flag offensive delete link

add a comment

Question Tools

3 followers

Stats

Asked: 2020-05-19 03:58:20 -0600

Seen: 1,174 times

Last updated: Jun 09 '20

Gazebo Real Time Factor going down edit

1 Answer

Question Tools

Stats

Related questions

Gazebo Real Time Factor going down