|
Apache configures this default. Do you have some URL to indicate why they
configure it like such instead of another way? I'd be quite interested
since I have my production servers set to below spec...
<<It would seem like a silly setting to put in the default install of Apache
if it just breaks the web server. Keeping in mind apache's slogan :
durability & correctness first, performance second.>> ?
I was searching around on the web and found the following relevant links..
http://thingy.kcilink.com/modperlguide/performance/KeepAlive.html
http://httpd.apache.org/docs/keepalive.html <-- not that useful
http://www.apache.gamma.ru/docs/misc/fin_wait_2.html <-- old but interesting
Thanks,
Peter
> -----Original Message-----
> From: andreas.koenig@xxxxxxxx [mailto:andreas.koenig@xxxxxxxx]
> Sent: Tuesday, May 01, 2001 4:34 PM
> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Cc: pmueller@xxxxxxxxxxxx; ja@xxxxxx; Joseph Mack
> Subject: Re: Netscape persistence [Was Re: success: LV-NAT working
>
>
> >>>>> On Tue, 01 May 2001 16:38:11 -0400, Joseph Mack
> <mack.joseph@xxxxxxx> said:
>
> > If a client with persistent http connects through an LVS
> to real-servers with httpds
> > which can maintain a persistent httpd connection and the
> client asks for a web page
> > full of gifs, then I expect the html page will be first
> downloaded (opening a persistent
> > connection to the real-server). The client will then
> issue several commands of the type
> > "GET /foo.gif"
>
> > If these requests go over the established connection,
> then the ActConn counter on ipvsadm
> > won't change (will stay at 1).
>
> > However this doesn't happen. The counters go up as seen
> by ipvsadm. Each gif must
> > be requested through a new connection.
>
> > so I still don't understand what's going on
>
> > Any ideas anyone?
>
> Netscape just doesn't use a single connection, and not only Netscape.
> All major browsers fire mercilessly a whole lot of connections at the
> server. They just don't form a single line, they try to queue up on
> several ports simultaneously...
>
> >> # KeepAliveTimeout: Number of seconds to wait for the
> next request from the
> >> # same client on the same connection.
> >> #
> >> KeepAliveTimeout 15
>
> ...and that is why you should never set KeepAliveTimeout to 15 unless
> you want to burn your money. You keep several gates open for a single
> user who doesn't use them most of the time while you lock others out.
>
> --
> andreas
>
|
