Unexpected CPU usage persists with BEST_EFFORT QoS and 500 ms deadline on low‑traffic ROS 2 topic
When deploying a ROS 2 node that publishes at 1 Hz on a lightly loaded system, the intention is to lower CPU consumption by setting the publisher’s QoS profile to reliability: BEST_EFFORT and increasing the deadline to 500 ms, as the middleware then avoids retransmissions and drops late samples instead of buffering them. Despite applying these QoS settings,