-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kenneth Burgener wrote: > The overhead is due because when building a "new" connection there is a > lot of hurdles to pass: > > * Creating a TCP/IP socket > * Firewall rules are generally always about "new" connections so > this is a delay point > * Apache has to receive the socket request > * Apache then has to assign a worker to perform the request > > All of this is avoided for the multiple items on a single KeepAlive request.
And since he's specifically talking about HTTPS, the encryption overhead gets even worse. I'm not surprised at all to hear that keep-alive sped up the server by that much. Corey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqMr+wACgkQwNwjtxfqOkOglACeOtlt2HbEStndhImF01PZegjw Qf0AnjgpOST2qn3j+4oqQ/bYsHzVZ9Br =T/oB -----END PGP SIGNATURE----- /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
