Configure TCP socket to reduce latency

TCP_NODELAY disables Nagles algorithm. This improves latency (reduces),
but worsens overall throughput. For the purpose of bridging a CAN bus
over a network connection to socketcand (and given the relatively low
overall bandwidth of CAN), optimizing for latency is more important.

TCP_QUICKACK disables the default delayed ACK timer. This is ~40ms in
linux (not sure about windows). The thing is, TCP_QUICKACK is reset when
you send or receive on the socket, so it needs reenabling each time.
Also, TCP_QUICKACK doesn't seem to be available in windows.

Here's a comment by John Nagle himself that some may find useful:
https://news.ycombinator.com/item?id=10608356

"That still irks me. The real problem is not tinygram prevention. It's
ACK delays, and that stupid fixed timer. They both went into TCP around
the same time, but independently. I did tinygram prevention (the Nagle
algorithm) and Berkeley did delayed ACKs, both in the early 1980s. The
combination of the two is awful. Unfortunately by the time I found about
delayed ACKs, I had changed jobs, was out of networking, and doing a
product for Autodesk on non-networked PCs.  Delayed ACKs are a win only
in certain circumstances - mostly character echo for Telnet. (When
Berkeley installed delayed ACKs, they were doing a lot of Telnet from
terminal concentrators in student terminal rooms to host VAX machines
doing the work. For that particular situation, it made sense.) The
delayed ACK timer is scaled to expected human response time. A delayed
ACK is a bet that the other end will reply to what you just sent almost
immediately. Except for some RPC protocols, this is unlikely. So the ACK
delay mechanism loses the bet, over and over, delaying the ACK, waiting
for a packet on which the ACK can be piggybacked, not getting it, and
then sending the ACK, delayed. There's nothing in TCP to automatically
turn this off. However, Linux (and I think Windows) now have a
TCP_QUICKACK socket option. Turn that on unless you have a very unusual
application.

"Turning on TCP_NODELAY has similar effects, but can make throughput
worse for small writes. If you write a loop which sends just a few bytes
(worst case, one byte) to a socket with "write()", and the Nagle
algorithm is disabled with TCP_NODELAY, each write becomes one IP
packet. This increases traffic by a factor of 40, with IP and TCP
headers for each payload. Tinygram prevention won't let you send a
second packet if you have one in flight, unless you have enough data to
fill the maximum sized packet. It accumulates bytes for one round trip
time, then sends everything in the queue. That's almost always what you
want. If you have TCP_NODELAY set, you need to be much more aware of
buffering and flushing issues.

"None of this matters for bulk one-way transfers, which is most HTTP
today. (I've never looked at the impact of this on the SSL handshake,
where it might matter.)

"Short version: set TCP_QUICKACK. If you find a case where that makes
things worse, let me know.

John Nagle"

can/interfaces/socketcand/socketcand.py

@@ -13,6 +13,7 @@
 import time
 import traceback
 from collections import deque
+import os
 
 import can
 
@@ -79,6 +80,7 @@ def __init__(self, channel, host, port, can_filters=None, **kwargs):
         self.__host = host
         self.__port = port
         self.__socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+        self.__socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1)
         self.__message_buffer = deque()
         self.__receive_buffer = ""  # i know string is not the most efficient here
         self.channel = channel
@@ -120,6 +122,8 @@ def _recv_internal(self, timeout):
             ascii_msg = self.__socket.recv(1024).decode(
                 "ascii"
             )  # may contain multiple messages
+            if os.name != "nt":
+                self.__socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_QUICKACK, 1)
             self.__receive_buffer += ascii_msg
             log.debug(f"Received Ascii Message: {ascii_msg}")
             buffer_view = self.__receive_buffer
@@ -173,9 +177,13 @@ def _recv_internal(self, timeout):
     def _tcp_send(self, msg: str):
         log.debug(f"Sending TCP Message: '{msg}'")
         self.__socket.sendall(msg.encode("ascii"))
+        if os.name != "nt":
+            self.__socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_QUICKACK, 1)
 
     def _expect_msg(self, msg):
         ascii_msg = self.__socket.recv(256).decode("ascii")
+        if os.name != "nt":
+            self.__socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_QUICKACK, 1)
         if not ascii_msg == msg:
             raise can.CanError(f"{msg} message expected!")