KeepAlive Process

[AmishPatel]

My admin has turned the process off and the server has improved a lot, however, my question is what that/s the trade off? What do I lose by not having it on?

[adrianchew]

Keepalive keeps a single connection for a session - that session could be getting a Web page plus the associated graphics and all. Without it - each HTTP request requires a new connection to be established to the server, the transfer done, and then the connection is torn down. But the overhead of that is typically less than if you ran out of memory due to too many sessions being open at the same time as each Web server process takes up a certain amount of memory.

[f0urtyfive]

Hehe Hi Amish (I'm his admin) I read these forums too :P

Anyway, He's asking because recently I moved all the pictures into a thttpd server and then realized that keepalive was still on apache with nothing to be gotten through the tunnel, so I turned it off. Kills all the wasted memory. I'd like to get the thttpd working with keepalive, but the only patches I've found were from like 5 versions ago.... the instant I turned keepalive on apache off our mem usage went down like 200 megs (resource hog).

Anyway, Just lettin everybody know.

[adrianchew]

I would suggest trying lighttpd...

http://www.lighttpd.net/

I use it for not only graphics but the main site too - PHP FastCGI. You see about a 20-25% improvement over Apache/PHP plus a lot smaller memory footprint.

[f0urtyfive]

Actually after I posted that message I installed lighttpd instead of thttpd for the image server, it's working well with keepalive on, it doesnt seem like the images load randomly now.