ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The app isn't actually "doing nothing." It's having to follow the simulator's time, which will take some CPU.

On my Macbook Pro, 2.2Ghz, I can get the same CPU numbers if the simulator is publishing time at 1Khz, i.e. that is the load of deserializing 1000 clock messages a second. The clock rate is a function of your simulation step size and the speed of the simulation. You may, for example, to consider a smaller step size if you don't need that level of clock fidelity.

There are some tweaks that rospy can use to lower the CPU usage, but these would be small improvements. The fact is, running nodes in simulated time will add CPU load.