<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Depends on what the connections are, really. If these are lots of long-lived connections, that'll have a very different result than lots of short connections. If the system has 99% short-lived http requests and 1% SSH connections that'll be tuned differently than for the inverse. <br><br>Sent from my iPhone</div><div><br>On Aug 5, 2013, at 3:33 PM, leam hall <<a href="mailto:leamhall@gmail.com">leamhall@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Any good things to look at for tuning TCP on a machine with a lot of incoming connections? So far I'm looking at<br><br>net.ipv4.tcp_keepalive_time<br><br clear="all"><div>Any other recommendations?<br><br>
Thanks!<br><br>Leam<br></div><div>-- <br><div><a href="http://leamhall.blogspot.com/" target="_blank">Mind on a Mission</a></div>
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Ale mailing list</span><br><span><a href="mailto:Ale@ale.org">Ale@ale.org</a></span><br><span><a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a></span><br><span>See JOBS, ANNOUNCE and SCHOOLS lists at</span><br><span><a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a></span><br></div></blockquote></body></html>