From: Thomas O'Dowd <tpodowd@ge...> - 2010-04-14 06:33:25
Thanks for pulling my last patch and letting me know the correct pull
syntax. As such, here is another feature you might be interested in.
It's a new configuration option, some examples are:
# Default behavior
keepalive_maxuses = nolimit
# Close persistent connections after 200 requests.
keepalive_maxuses = 200
As the name suggests, this lets the admin decide the max number of
requests it will allow over the same connection when using keepalive.
The default retains the current behavior which does not apply any limit.
This option again is (for us anyway) aimed at erlang garbage collection
problems with long running persistent connections. It is also useful for
other reasons I'm sure.
Here is the pull url:
# git pull git://github.com/tpodowd/yaws.git keepalive_maxuses
This patch was written by one of the other guys on the team and I've
modified it slightly, added configuration and a man page entry for
inclusion in yaws. Thanks Saito-san!
Anyway, our memory woes are much improved with these last two steps (the
process_options and keepalive_maxuses configs) so I'm hoping others will
see a benefit too.
Get latest updates about Open Source Projects, Conferences and News.