ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop bandwidth starvation in high-throughput networks by switching from Strict Priority Queueing to Weighted Fair Queueing (WFQ). Learn how to balance latency and fairness.
DDS Quality of Service Configuration In ROS 2, the Data Distribution Service (DDS) layer manages communication through Quality of Service (QoS) profiles. When implementing a system where late-joining subscribers must receive the most recent state updates, the Transient Local durability setting is used on the publisher to store messages for future subscribers
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,
Resource Allocation Trade‑offs In Kubernetes, the relationship between resource requests and limits defines a pod’s Quality of Service (QoS) class. Setting requests equal to limits yields a Guaranteed pod, protecting it from eviction during node memory pressure. Setting requests lower than limits creates a Burstable pod, allowing it to use spare node capacit
Goal: Verify whether the default QoS durability settings of the tf2 static transform broadcaster in ROS 2 Foxy (VOLATILE) and ROS 2 Humble (TRANSIENT_LOCAL) prevent reliable exchange of /tf_static messages when nodes built on different distributions communicate. Constraints: Foxy nodes publish with VOLATILE durability while Humble nodes expect TRANSIENT_LOCA
npss
ros
kubernetes