Very high latency when using ROS tools over WiFi [closed]
At a recent competition, we noted that ROS tools sometimes take extremely long to start up when running in less than perfect WiFi conditions. Other programs (multiple SSH connections to the robot) seemed to work fine and felt snappy, while starting up ROS tools like rviz and rqt took more than 5 minutes from start in terminal to UI actually coming up. Of course, some overhead is to be expected due to topic connections/negotiation with Master, but especially in case of rqt I don't see why it should take that long. We've been using ROS since years and were able to cope with pretty bad WiFi, but our most recent experience was pretty bad, so I'm looking for any pointers. I do not rule out some sort of network misconfiguration on our part (routing tables etc.), so any suggestions what to look for are appreciated.
Do you have any network captures while things were starting up? I've seen things taking a long time when multiple concurrent attempts were all waiting for their timeout to occur. Having a traffic capture really helps in case of network issues.
Did you get a chance to debug anymore?