2024 04 02 Eclipse iceoryx developer meetup

Eclipse iceoryx developer meetup

Date: 2024/03/05

Time: 17:00 CET

Link: https://app.element.io/jitsi.html#conferenceDomain=meet.element.io&conferenceId=JitsiVtfrqukadefbqiqfxryxabai&userId=&roomId=!AooDAAwkyNWwkMElpt%3Agitter.im&roomName=eclipse%2Ficeoryx&startWithAudioMuted=true&startWithVideoMuted=true&language=en

https://giphy.com/gifs/hail-hypnotoad-rou0CTAp6Z8VW/fullscreen

Attendees

• Mathias Kraus, ekxide IO GmbH
• Alex Nolley, Latitude AI
• Graham Palmer, Latitude AI

Agenda

1. Look at the open tasks from previous meetings, 10 min, Mathias
   • Adding the new meeting date to the ROS 2 calendar
   • Update iceoryx.io to inform about the new Rust implementation - maybe also register iceoryx.rs - how to restructure iceoryx.io for the new Rust implementation
2. What's the state of the iceoryx1 v3.0 release and what needs to be done to bring it over the finish line, 10 min, Mathias
3. How to move forward with iceoryx1, 20 min, Mathias
4. UsedChunkList is slow for large capacity
5. Memory size of endpoints (subscriber, clients) is huge when number of chunks an endpoint can hold will increase (e.g. 200k)

Minutes

1. No work done
2. Needs to be coordinated in #2189
3. Postponed
4. Changing the data structure solves the problem
   • preserving API might be challenging for untypted API
   • FixedPostionContainer might help with backward compatibility
     • would need some API adjustment
5. The endpoints need to become a bit more dynamic
   • this needs quite a lot of refactoring in the ports since the capacity of the samples, subscriber, etc. is a template parameter
   • this would need to become more like the iceoryx2 architecture
   • alternatively, the structures could work on non-contiguous memory and dynamically allocate memory from a pool allocator in order to grow the data structures

Topics for future meetings

1. Move C-binding to separate repo?
   • #2030