Why is ROS slower than a normal TCP connection?
Why is ROS connections slower than a normal TCP socket connect?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Why is ROS connections slower than a normal TCP socket connect?
ROSTCP is an adapter that lets ROS send messages over TCP for topics; not for general use.
If you want a TCP socket, use the standard OS interface for creating a TCP socket.
Please check this
Asked: 2017-12-11 00:18:15 -0500
Seen: 330 times
Last updated: Dec 11 '17
Differences between ROS and Player.
Creating COLLADA (.dae) files for visual tag in Gazebo/ROS
Ros ultrasonic sensor Rviz Error
Turning lights On and Off on Gazebo with ROS
roscd: No such package/stack 'turtlebot_navigation/'
Implementation of two subscribers
Nodelet performance vs number of instances
Unable to download model manifests
use custom ompl instead of ros own ompl
How to add image texture to gazebo as material through blender settings
Can you clarify what is slower? Setting up connection, sending data (and then: bw or latency), tearing them down, something else?
I mean while sending and receiving data its slower than a TCP socket connection without ROS framework.
How are you measuring this? If you are comparing sending a raw array of bytes versus publishing and receiving messages, then that is not a correct comparison.