Nagle is something different, what you are facing is delayed ACK: TCP
tries to reduce the amount of small packets by only ACKing every 2nd
segment. To reduce your delays, you have to make sure that your
webserver doesn't wait to send data until the first segment is ACKed.
This is also called the "sliding window" mechanism. I can't currently
tell you how to achieve this since I don't know the webserver. Maybe
next week I can tell you more when we get the Luminary-http sources.
The defines below at least look OK to achieve good throughput...
Simon
gregoryhouse wrote:
Hi,
I have a web server (Luminary Micro contrib module with SSI and CGI). The page
content is sent in few parts. When server sends a part, web browser waits 200ms
before sending ACK.
I think there is nothing I can do with this, but I hope you could help me
somehow. I read a lot about 200 ms delays, Nagle, but the problem still exist.
Wireshark capture file is attached.
Settings:
#define TCP_WND 4096
#define TCP_MSS 1460
#define TCP_SND_BUF (4 * TCP_MSS)
Best regards.
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
