-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow your steps, but at the time of publication the prompt did not use the loan message #30
Comments
export RMW_IMPLEMENTATION=rmw_fastrtps_cpp |
ros2 version is humble |
humble loan messages is turned off by default and needs to be opened manually :export ROS_DISABLE_LOANED_MESSAGES=0 After the configuration was successful, testing found no difference in latency, and even more volatile in some cases. But the memory consumption is smaller [INFO] [1724408813.173785288] [shm_image8m_listener]: get-image8m-transport-time: 6.068 [INFO] [1724408805.494155807] [image_listener]: get-image-transport-time: 5.381 The program runs in docker |
did you copy the file to the home folder? https://github.com/ZhenshengLee/ros2_shm_msgs/blob/humble/config/shm_fastdds.xml
I didn't test it in docker, but I am sure the
It's the recent new feature, I didn't test with it.
Could you please check if the datasharing of fastdds is turn on? in fastdds, zerocopy = loaned api + datasharing. see https://fast-dds.docs.eprosima.com/en/v2.6.9/fastdds/use_cases/zero_copy/zero_copy.html#writing-and-reading-in-zero-copy-transfers Lines 110 to 117 in 42fde5f
The config of fastdds was confirmed by ros2/rmw_fastrtps#636 , but I cannot gurantee it works for the year of 2024. You can take a look the rmw_fastrtps repo for any updates. |
Checked. It's already on /dev/shm/fastrtps_2191af2cf197f25e /dev/shm/fastrtps_d33d7dcdce88dd25 /dev/shm/fast_datasharing_01.0f.3d.ea.16.f9.be.d3.00.00.00.00_0.0.12.3 There may be a configuration problem that is different from the version of fastdds you are using. It needs to be revised and studied again. |
./image1m_talker
[INFO] [1724397612.482477407] [rclcpp]: Currently used middleware can't loan messages. Local allocator will be used.
[INFO] [1724397612.483361236] [shm_image1m_talker]: Publishing
[INFO] [1724397612.583124064] [shm_image1m_talker]: Publishing
[INFO] [1724397612.682550347] [shm_image1m_talker]: Publishing
[INFO] [1724397612.782653069] [shm_image1m_talker]: Publishing
[INFO] [1724397612.882653885] [shm_image1m_talker]: Publishing
[INFO] [1724397612.982543701] [shm_image1m_talker]: Publishing
The text was updated successfully, but these errors were encountered: