The delayed ACK option is selected. I will try to deselect it and make end to end testing before going further with investigation. Thank you very much for the hint.
пт, 1 вер. 2023 р. о 01:04 Gregory Nutt <spudan...@gmail.com> пише: > > On 8/31/2023 3:39 PM, Petro Karashchenko wrote: > > Hello, > > > > I'm having an issue with a network based application on NuttX. > > I have a HTTP server that is built with the help of the "netlib_server" > > interface. When I'm trying to access my server with curl multiple times > in > > a row I see that there is a gap close to 500ms on the PC side when > > accessing the device. > > > > I think maybe this is somehow related to a case where each time a new > > request is accepted the client socket is created, handled and closed? I > > will deepdive into this of course and will analyze wireshark logs, but > > maybe someone has any guesses or met similar issues in the past? I mean > > maybe there is some kind of "blacklist" or TCP/socket configuration that > > prevents new connections from being established for a certain period of > > time? > > > > Best regards, > > Petro > > You will have to use wireshark to get to the bottom. It sounds like > there is some delay or timeout that is causing the issue. Perhaps in the > 3-way handshake. It taks 500ms for a missing ACK to be detected. Are > you using delayed ACKs? That delay is 500ms too. > > >
