[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Delays over WiFi

From: Mortimer76
Subject: Re: [lwip-users] Delays over WiFi
Date: Fri, 20 May 2016 06:15:50 -0700 (MST)

Hi Sergio, thanks for your help. I will check that.
As far as I remember in my application I do not really wait for an ACK after sending the header. The content is sent directly after the header without actively waiting for the response. But maybe that happens in the background automatically when I send data 2 times with lwip send method.
Is there a chance to reduce some timeouts in lwipopts.h so that my app would react on possible lost telegram earlier and not just after 5 seconds?


Am 20.05.2016 2:25 nachm. schrieb "Sergio R. Caprile [via lwIP]" <[hidden email]>:
You could trim your memory, there are some threads on this on the list,
I suggest you search for them.
However, what needs to be optimized is your application.
Check the examples on the contrib tree, you should check for TCP buffer
room and fill it as much as possible. Your TCP_MSS is 536, that means
you could easily send (at least) that many bytes without waiting for an
ACK, but you are stopping at the CRLFCRLF after the header (250 bytes)
and waiting for an ACK before sending the content (14 bytes).
If you need more help on this, I suggest you rename the thread to
something including 'socket' and perhaps 'performance optimization' or
something like that. It is good practice to keep a [was: ...] tag (or am
I too old?)

lwip-users mailing list
[hidden email]

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from Delays over WiFi, click here.

View this message in context: Re: Delays over WiFi
Sent from the lwip-users mailing list archive at Nabble.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]