[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #20506] LWIP: TCP Layer Performance
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #20506] LWIP: TCP Layer Performance |
Date: |
Wed, 18 Jul 2007 10:56:08 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 |
Update of bug #20506 (project lwip):
Category: TCP => Contrib
Item Group: Feature Request => Faulty Behaviour
_______________________________________________________
Follow-up Comment #4:
BTW: Attaching an ethereal/wireshark capture file is worth much more than
only seeing the image you attached. E.g. we can see the MAC/IP/TCP headers,
maybe there are problems there?
> i observed that for a http request the time taken from the starting of
tcp_input function to function of http layer is 150ms which I think can be
improved.
That is definitively not normal! As it works fine on other platforms, I
suggest this might be a memory limitation (problem with your memory settings
in lwipopts.h)
Anyway, looking at your trace, the only real gap is between the first and
second HTTP response packet for each JPG. That might be a limitation of the
http server or of your memory.
What disturbs me is that there is no call to tcp_output in the whole httpd.c
file. Calling tcp_write simply enqueues the data to send, without calling
tcp_output, no data will be sent right away. Data will only be sent by timer
functions, which are running about every 250 ms for tcp. This is the best
explanation for your delay, after all.
This is not an error in lwIP itself, but in the http server!
As this http server is also included in our contrib module, I'm setting this
to 'Faulty Behaviour' in module 'Contrib'.
BTW: thanks for reporting this.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?20506>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Vipin, 2007/07/17
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Simon Goldschmidt, 2007/07/17
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Frédéric Bernon, 2007/07/17
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Vipin, 2007/07/18
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Vipin, 2007/07/18
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance,
Simon Goldschmidt <=
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Simon Goldschmidt, 2007/07/18
- [lwip-devel] [bug #20506] LWIP: TCP Layer Performance, Frédéric Bernon, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Simon Goldschmidt, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Frédéric Bernon, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Simon Goldschmidt, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Frédéric Bernon, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Simon Goldschmidt, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Jim Pettinato, 2007/07/18
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Vipin, 2007/07/19
- [lwip-devel] [bug #20506] HTTP server doesn't call tcp_output, Vipin, 2007/07/19