eclipse-ecal/rmw_ecal

support static type support (based on google protobuf)

rex-schilasky opened this issue · 0 comments

Even the underlaying eCAL is using shared memory for ipc and so can share data with very low latency the serialization of complex ROS messages like large PointClouds is consuming a lot of performance and increasing the overall latency significantly. This is because we implemented dynamic type support only.

We need to add static type support too and I would propose we use the Google Protobuf message format for that static implementation internally (like we tried it for the dynamic one). The big advantages of such an implementation would be

  • standard serialization format
  • high serialization / deserialization performance
  • all eCAL tools (monitor, recorder, player, python, matlab interfaces) can make use of protobuf to process data in a generic way