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

Poor move_base performance on Nvidia Xavier

asked 2019-07-26 15:33:17 -0500

adriandole gravatar image

I recently migrated a robotics project from the TX2 to the Xavier, and my navigation has been functioning poorly. The map update loop frequently misses its update loop of 10 Hz, whereas the exact same software with the same settings very rarely had this problem on the TX2.

What I've tried:

  • All of my sensors are publishing at rates over 10 Hz
  • Two separate Xavier devices flashed with the newest firmware.
  • Both TrajectoryPlannerROS and DWAPlannerROS
  • Maximum performance mode on the Xavier
  • CPU usage is low. move_base isn't even using all of a single core. The Xavier is significantly faster than the TX2. I'm fairly confident this isn't a CPU performance issue.

The only difference is that the Xavier is running Melodic and the TX2 was running Kinetic. My software is unchanged. I looked through the default values for move_base in Melodic and Kinetic and they appear to be identical. Is there anything else I should try?

edit retag flag offensive close merge delete



Did you remember to build the navigation packages with optimisations enabled?

gvdhoorn gravatar image gvdhoorn  ( 2019-07-28 12:37:03 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2019-07-29 09:25:06 -0500

adriandole gravatar image

Enabling optimizations appears to be the fix; I compiled with Catkin using -DCMAKE_BUILD_TYPE=Release. I'm not compiling move_base or any other navigation packages directly so I'm not sure why this works but it does.

edit flag offensive delete link more

Question Tools



Asked: 2019-07-26 15:33:17 -0500

Seen: 265 times

Last updated: Jul 29 '19