Nav2 modules reach 100% usage of the CPU about navigation2 HOT 4 CLOSED

Nav2 is not a single threaded application. I'd have to review the stack, but I think its ~10-20 threads, depending on what you have running. 120% of a core seems about right and inline with our published metrics. Frankly, its amazing we only use 1.2 of those weak, low power ARM cores to run all of autonomous navigation!

That is not "only" running Nav2, I see some accounts daemon, microros, rosbridge themselves summing up to 1.6 cores (more than Nav2!). The other lidar/base drivers/teleop nodes also add up, but seem more or less inline with what I'd think (though, 8% for a teleop/odom publisher node seems excessive - what are these, python?)

This is not a safe configuration. You're thrashing the CPU and memory, I would not attempt to operate a robot under these compute conditions unless it was a small toy robot that if it had problems in an R&D lab would be no big deal. You need more compute.

from navigation2.

Thank you for your quick response! It's true that I must remove a lot of garbage apart from Nav2, but.. could you tell me how can I launch the nav2_bringup in "release mode" or something that doesn't make the component container run in log-level info? I'm so lost over here sorry

from navigation2.

I don't understand what you mean or what behavior you're trying to remove.

from navigation2.

I'd like to know how would you try to reduce at maximum the CPU usage (talking only about Nav2 modules)

My only goal is to navigate on the ground with a 2-wheeled differential robot at speeds about 1m/s

from navigation2.