qrb_ros_benchmark extends the upstream ros2_benchmark framework with first-class awareness of QRB transport types and dmabuf_transport types — so you can measure zero-copy wins apples-to-apples against stock sensor_msgs.
If you’re evaluating Qualcomm for robotics, this is how you verify the perf claims. Same harness, same methodology, three transport types — pick the one that tells you what you need.
What it measures
Out of the box, the package knows how to benchmark:
The per-type awareness is what makes the apples-to-apples comparison possible — running
ros2_benchmark against sensor_msgs::Image and then against qrb_ros::transport::type::Image with the same producer and consumer isolates the cost of serialization + memcpy from everything else.
Quick start
1
Install on Ubuntu on Qualcomm® IoT platforms
2
Run a benchmark
Usage follows the upstream
ros2_benchmark conventions — see the upstream README for the full flow. The typical pattern is a launch file that wires your node under test + ros2_benchmark’s data-loader and monitor nodes, and a Python driver that runs the measurement sweep.Why this helps
Extends
ros2_benchmark with awareness of QRB transport types and DMA-buf types — measure zero-copy wins apples-to-apples against stock sensor_msgs. Pairs naturally with qrb-ros-dds-optimizer.mdx, which uses ros2_benchmark as its measurement harness.
Related
qrb-ros-transport.mdx— the transport being measured.qrb-ros-dds-optimizer.mdx— usesros2_benchmarkas its measurement loop, so a benchmark you wire up here can drive the DDS optimizer too.- Upstream:
qualcomm-qrb-ros/qrb_ros_benchmark,ros2_benchmark.