| 2:10 am on Oct 29, 2009 (gmt 0)|
|Is anyone here actively tuning the TCP/IP stack on their webserver OS ? |
We'll take that as a "no", shall we? ;) Have you had any good results so far with your tweaking?
| 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 :-)
| 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.
| 10:56 pm on Nov 25, 2009 (gmt 0)|
It depends on the application, but if connection tracking is not needed and packet sizes are not to large, you could switch from TCP to UDP.
| 9:50 pm on Dec 1, 2009 (gmt 0)|
|you could switch from TCP to UDP. |
Not an option. UDP breaks NAT and Firewall traversal (if user can access my webpage, I know that TCP/IP port 80 will work).