Joshua, Thanks a lot for you reply. I also think about the possible explanation. Theoretically, Without "KeepAlive On", Apache parent will pick whatever needed number of multiple children to handle multiple requests in parallel. However, in the condition of "KeepAlive On", a specific child, which has the connection ESTABLISHED with the client, will handle the multiple requests from the same client sequentially. It slows down the performance in the condition of large number of objects/files in a single hit. In the opposite, the "KeepAlive Off" would perform faster since Apache will handle multiple requests by multiple children simultaneously in parallel. Do you think the above explanation makes sense? Thx, Q.Xie --- Joshua Slive <joshua@xxxxxxxx> wrote: > On 8/10/06, Qingshan Xie <xieq_49@xxxxxxxxx> wrote: > > Hi,All, > > > > We have apache-2.0.54 installed on Solaris and > > Linux boxes. We did a bounch of Load-Test with > > KeepAlive On or Off on multiple jpg, gif, text > files. > > The test results are discourage. The webServer > has > > slower response time when KeepAlive is On compared > to > > the condition when KeepAlive is Off. Can someone > tell > > me what chould be wrong, or what is the trick to > make > > the KeepAlive function as expect? > > That's the beauty of load testing software. It all > depends on how > things are measured. > > If the load-testing clients are not using > keep-alives, the server will > almost certainly be slower with keep-alives turned > on, because a bunch > of your processes will be stuck waiting for requests > on keep-alive > connections that never come. Even if the clients > *are* using > keep-alives, you could see the same effect (to a > lesser degree) if > they don't balance perfectly with the server. > > In the real world, people with very busy servers and > a limitted > MaxClients (because of memory issues, perhaps) often > need to turn down > KeepAliveTimeout to keep up with the load. A better > solution in > development in 2.2/2.3 is the event mpm, which > transfers keep-alive > processing to a separate thread where it doesn't tie > up the worker > threads. > > Joshua. > > --------------------------------------------------------------------- > The official User-To-User support forum of the > Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for > more info. > To unsubscribe, e-mail: > users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: > users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: > users-help@xxxxxxxxxxxxxxxx > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|