RoverLog Networking Performance

23 views
Skip to first unread message

Tom Mayo

unread,
Jan 23, 2013, 8:50:43 AM1/23/13
to rove...@googlegroups.com
Folks,

I've been doing some experimenting with RoverLog networking, and I can reproduce issues folks have been reported with very sluggish performance.  It's nasty.

These happen when messages are sent to nonexistent IP peer nodes with the current UDP scheme.

The old scheme used TCP, but did not create a permanent socket between nodes.  It opened and closed a socket with each message.  This was TERRIBLE because of the amount of IP traffic it created.

The UDP scheme is TERRIBLE if a node disappears temporarily or never existed.  There is a long hang with each network attempt which I did not anticipate (it's UDP after all).

So I am working on a scheme that uses TCP but creates permanent sockets between nodes and grooms and maintains these sockets.  I think this will be a good scheme long term.  It'll take me a little while to get this going, but this should really fix issues where networks are spotty or where the settings represent a full multi-op system but some stations are not powered up.

Please bear with me as I revamp RoverLog networking for the next release.

Thanks,
Tom, N1MU.

Steve Meuse

unread,
Jan 23, 2013, 8:55:14 AM1/23/13
to rove...@googlegroups.com


 If you could, add some sort of status window that shows currently connected hosts/endpoints. I'll even take a command line approach. "wish roverlog.tcl --showhosts" etc. I always like having the ability to see what's happening at a lower level. 

Thanks!

-Steve
N1JFU



--
You received this message because you are subscribed to the Google Groups "RoverLog" group.
To post to this group, send email to rove...@googlegroups.com.
To unsubscribe from this group, send email to roverlog+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/roverlog/-/Nvi4mMZjc6QJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--

-Steve

Tom Mayo

unread,
Jan 23, 2013, 10:10:34 AM1/23/13
to rove...@googlegroups.com
Steve,

Visibility is important.

The previous scheme was to have status on the Station Info window.  The peer buttons had black text for peer ok and red text for peer lost.  You'd click the button to try to re-establish comms.

What do you think of returning to that paradigm?

Tom.  

Tom Mayo

unread,
Jan 25, 2013, 12:30:14 PM1/25/13
to rove...@googlegroups.com
The new networking scheme is almost ready.  Check out the screenshot of the new Communications Status window.  This is in the works for 2_7_0.
rl-comms_stat.png
Reply all
Reply to author
Forward
0 new messages