This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Idle timeout and maximum # of sockets for athttpd
- From: "Øyvind Harboe" <oyvind dot harboe at zylin dot com>
- To: "eCos Disuss" <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 12 Dec 2007 12:07:07 +0100
- Subject: [ECOS] Idle timeout and maximum # of sockets for athttpd
I don't quite understand CYG_HTTPD_SOCKET_IDLE_TIMEOUT in detail, but
it is hardwired to 300 seconds which appears to be rather long for the
default maxim # sockets (16).
Issuing 8 or so http requests, e.g. via wget, in rapid succession will
cause the server to
sit there for a while before recovering. No requests appear to be
dropped on the floor,
but if there is no response from a server on the LAN within 30 seconds
it will be very hard to
distinguish that from a crashed server for most users. Servicing an
actual request takes << 1 second
in my tests and by increasing the maxim # of sockets to 64, the
athttpd appeared quite robust. Still
it is possible to overflow it, but the by the time it has overflowed
I'd expect sockets to start getting
freed again...
Any thoughts?
Make CYG_HTTPD_SOCKET_IDLE_TIMEOUT configurable via cdl w/default being some
multiple of maximum # of sockets?
Could CYG_HTTPD_SOCKET_IDLE_TIMEOUT be set to 0? What would happen?
--
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss