Skip to content
Tool to test the performance of pub/sub based communication frameworks.
Branch: master
Clone or download
EduPonz and esteve generate and load default XML file to configure whitelists (#69)
* generate default XML to donfigure whitelists and load it

* using dom to set attributes and whitelist separated by spaces

* Generate XMl usign xml.dom.minidom and script documentation

* do not remove the xml version line
Latest commit 04430ed Jun 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
performance_test generate and load default XML file to configure whitelists (#69) Jun 19, 2019
LICENSE Initial commit Jun 12, 2018 Merge pull request #58 from ApexAI/azure-pipelines May 3, 2019
azure-pipelines.yml Update to Dashing (#65) Jun 7, 2019

Build Status

Build Status


Version Support: ROS2 Crystal, Fast-RTPS 1.7.0

This test allows you to test performance and latency of various communication means like ROS 2, FastRTPS and Connext DDS Micro.

It can be extended to other communication frameworks easily.

A detailed description can be found here: Design Article


Building and running performance test

ROS 2:

Generating graphical plots

The script which generates the graphical plots needs matplotlib and pandas:

sudo apt-get install python-matplotlib python-pip
pip install pandas

How to build and run

source ros2_install_path/setup.bash
mkdir -p perf_test_ws/src
cd perf_test_ws/src
git clone
cd ..
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
source install/setup.bash
ros2 run performance_test perf_test --help

Plot results

After building, a simple experiment can be run using the following.

Before you start please create a directory for the output.

mkdir experiment
cd experiment

then run the test.

ros2 run performance_test perf_test -c ROS2 -l log -t Array1k --max_runtime 10

The generated log-files can then be plotted into a PDF file using:

ros2 run performance_test .

Batch run experiments (for advanced users)

Multiple experiments can be run using the following command:

python src/performance_test/performance_test/helper_scripts/

You need to edit the python script to call the performance test tool with the desired parameters.

Relay mode

Testing latency between multiple machines is difficult as it is hard precisely synchronize clocks between them. To overcome this issue performance test supports relay mode which allows for a round-trip style of communication.

On the main machine: ros2 run performance_test perf_test -c ROS2 -t Array1k --roundtrip_mode Main On the relay machine: ros2 run performance_test perf_test -c ROS2 -t Array1k --roundtrip_mode Relay

Note that on the main machine the round trip latency is reported and will be roughly double the latency compared to the latency reported in non-relay mode.

Memory analysis

You can use OSRF memory tools to find memory allocations in your application. To enable it you need to do the following steps, assuming you already did compile performance test before:

  1. Enter your work space: cd perf_test_ws/src
  2. Clone OSRF memory memory tools: git clone
  3. Build everything cd .. && ament build --parallel --build-tests --cmake-args -DCMAKE_BUILD_TYPE=Release
  4. You need to preload the memory library to make diagnostics work: export LD_PRELOAD=$(pwd)/install/lib/
  5. Run with memory check enabled: ros2 run performance_test perf_test -c ROS2 -l log -t Array1k --max_runtime 10 --check_memory

Note that enabling this feature will cause a huge performance impact.

Custom environment data

You can set the APEX_PERFORMANCE_TEST environment variable before running performance test to add custom data to the output CSV file. This information will then also be visible in the files outputted by the plotter script.


My Version: 1.0.4
My Image Version: 5.2
My OS Version: Ubuntu 16.04
ros2 run performance_test -c ROS2 -t Array1k


  1. When running performance test it prints ERROR: You must compile with FastRTPS support to enable FastRTPS as communication mean.

You need to build with --cmake-args -DPERFORMANCE_TEST_FASTRTPS_ENABLED=ON to switch from ROS 2 to FastRTPS.

Known Limitations

  • FastRTPS waitset does not support a timeout which can lead to the receiving not aborting. In that case the performance test must be manually killed.
You can’t perform that action at this time.