🚀 go-pugleaf

Hello,

I've posted about a few issues in regards to the TTcpClient socket component
and scokets in general lately.

My new problem is that when ACK'ing back to the server after receiving the
data, the ACK is taking around 200ms.  Completely unacceptable for the
application and I'm obviously doing something wrong.


Here's an example of the exchange.

GUI                              Server
Send ASCII cmd------->
    <--------------------ACK  cmd received(<1ms)
    <--------------------PSH Data in response to CMD (99ms  this too is slow
and we're working on it)
ACK Data received------>(200 ms after data received from server)

One thing noticeable is that the window size for the GUI is always set at
65535.  That seemed a bit strange to me.  I am using SendText and
ReceiveText for
handling socket i/o.  My assumption is that this is lower level in the stack
though.

Other notes,  the data size for each packet is quite small. So we are
typically sending a larger number of small packets rather than one large
packet.

Does anyone have a suggestion of things to look at or try, in order to get
the delay times down to a reasonable number.

Thanks,
Josh