For a web server, the socket connection are kept alive to save overhead. At which point the server should start to drop connection that doesn't have pending request and based on what premises?
- 1This would depend on any number of items: operating system, http server being used, memory, type and number of network interfaces. I am guessing this is more of a serverfault type question though.Sean– Sean2009-11-18 19:38:27 +00:00Commented Nov 18, 2009 at 19:38
- 1It looks like that this is a development issue rather than a configuration issues, so it looks like this site is the intended place for this question.monksy– monksy2009-11-18 19:39:29 +00:00Commented Nov 18, 2009 at 19:39
Add a comment |
1 Answer
Usually this is based on the operating system its self. Optionally to best account for performance, make this value an changeable option. [Put it in a properties file] The amount of connections open depends on your hardware, OS, and lengths of jobs performed by the clients. If the jobs performed by the server are light on network traffic and processing you may be able to get away with the maximum allowed open connections.
2 Comments
Jeff Cyr
You are probably right, the best value will be found out of usage and tweaking. I wanted to get an idea of the scale of the value, is it around 100, 1000, 10000... ?
monksy
Like I said, it depends. You could do an simulated annealing approach to get the optimal amount for normal usage.