You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without knowing your use case I still want to say: Zero-Copy sounds awesome, but what you rather should optimize for is performance, independent from where it comes from. As long as your messages are not "that big", one additional copy will not take enough time to be noticeable and you can often achieve more effect by optimizing other parts of your code (e.g. the protobuf pitfalls I mentioned). Our applications ran just fine in the past without zero copy.
So, what's your opinion about the need and the possibilities of the zero-copy in robotics system?
Do we really need the pure zero-copy?
Yes, and the bottleneck of only one copy makes me crazy!
50%
Yes, but the minimum copy is what I pursuit.
50%
No, because the current design of zero-copy api from rclcpp is not good enough.
0%
No, because the zero-copy is not the real crucial point in the robotics system.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Do we really need the pure zero-copy transport that avoid all the copys?
one of proposition views:
from ros-perception/image_common#212 (comment)
one of oppostion views:
from https://github.com/continental/ecal/discussions/660#discussioncomment-2738856
So, what's your opinion about the need and the possibilities of the zero-copy in robotics system?
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions