Introduction to Benchmarking. Developing and working on stabilizing an application from the scribbles to the final executing binary is a long and hard task. During this process developers may come across stability and per- formances issues. In addition to these issues, some specified QoS might be difficult to quantify. Solving these problems without the proper tools might be a frustrating and a tedious task lead- ing to reduce the developers efficiency. An adapted benchmarking tool could overcome most those development’s obstacles and reduce development time. There are different KPIs (Key Performance Indicators) that one might be interested into. In the framework of this micro-ROS project, the KPI can be freely chosen by the developer. In this way, the benchmarking tool will remain flexible and allow the community to constantly add some support for a lot of different KPIs. The problems to tackle are: • Out there, many benchmarking tools exist. Each of them targeting different KPIs • Platform dependency (Linux/Nuttx/Baremetal etc.) • Too few time/resources to code benchmarking tools for each platform and/or KPIs • Avoid code overhead: keep code clarity, • Avoid execution overhead: do not want to make the execution slower when benchmarking.
Introduction to Benchmarking. As this deliverable is only an extension of D5.6, we will not duplicate the description of benchmarking tools. Full description is in the D.5.6 [1]. The architecture has not changed since last year, only bugs have been fixed and support for the Zephyr OS has been added.
Introduction to Benchmarking. Developing a working and stable application from the scribbles to the final executing binary is long and hard task. During this process developers may come across stabilities issues, performances is- sues. In addition to these issues, some specified QoS might be difficult to quantify. Solving those problems without the proper tools might be frustrating, tedious tasks leading to reduce develop- ers efficiency. An adapted benchmarking tool could overcome all those development obstacles and increase development time. There are different KPI (Keep Performance Indicators) that one might be interested into. In the framework of this micro-ROS, the KPI can be freely chosen by the devel- oper. In this way, the benchmarking tool will remain flexible and allow the community to constantly add some support for a lot of different KPI. The benchmarking tool is also intended for embedded software benchmarking with low/none overhead intrusion. The problems we want to tackle are: • Out there, many benchmarking tools exist. Each of them targeting different KPIs
