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
In shared memory mode, after the number of topics in the system increases, the probability of the subscriber program does not match the publisher.
After releasing and printing, it is confirmed that the data information of some topics is lost in the EDP message. Do you know why? How to optimize this situation, and can I modify which configurations to send EDP information multiple times?
There are multiple programs subscribing to this topic in the system. Is it the publisher's EDP processing pressure caused by too many subscribers
The subscriber prints as follows:
writer proxy "fastdds statistics physical data"
writer proxy "fastdds statistics history2history latency'
writer proxy "fastdds statistics network latency"
reader proxy "ImpleResultInfo"
In fact, the topics published by the publisher are as follows:
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
-
In shared memory mode, after the number of topics in the system increases, the probability of the subscriber program does not match the publisher.
After releasing and printing, it is confirmed that the data information of some topics is lost in the EDP message. Do you know why? How to optimize this situation, and can I modify which configurations to send EDP information multiple times?
There are multiple programs subscribing to this topic in the system. Is it the publisher's EDP processing pressure caused by too many subscribers
The subscriber prints as follows:
writer proxy "fastdds statistics physical data"
writer proxy "fastdds statistics history2history latency'
writer proxy "fastdds statistics network latency"
reader proxy "ImpleResultInfo"
In fact, the topics published by the publisher are as follows:
writer "fastdds statistics physical data"
writer "fastdds statistics history2history latency'
writer "fastdds statistics network latency"
reader "ImpleResultInfo"
writer "gpsInfo"
writer "ctrlbackInfo"
writer "FaultInfo"
Beta Was this translation helpful? Give feedback.
All reactions