Curious to hear any results from people that have experimented with such low level tweaking. My current objective is to reduce a large volume of TCP/IP socket connections that are sitting in a WAIT_STATE pending an ACK from a client that will never arrive (because the client has gone offline). It seems there are proposed mechanisms for achieving this and having the client handle the WAIT_STATE rather than the server.
I'm not sure if Apache is already doing such things, haven't delved into that code yet.
Msg#: 4004220 posted 1:32 am on Nov 1, 2009 (gmt 0)
I would use the ideas from Yslow first before trying these. I do get a lot of hanging httpd sessions, and if my sites become slow, a cron job just restarts the httpd. Not a nice solution, but works for me.
Also you can search at the Apache forums, or join us at the ApacheCon next week :-)
Msg#: 4004220 posted 3:05 pm on Nov 25, 2009 (gmt 0)
Have you had any good results so far with your tweaking?
It's been, let's say, interesting. I've learned a lot about the lower level workings of TCP/IP, SYN and ACK signals etc and how they can get delayed but not ignored (part of the protocol design).
But I can't say that I've found anything particularly useful just yet.
I would use the ideas from Yslow first before trying these.
I'm actually tweaking a TCP/IP based application which isn't for the web. I thought of asking because of course HTTP servers are essentially TCP/IP based. I'll take a look at Yslow though - there might be some useful config tidbits in there - thanks for the heads up.