Hi Everybody, in the incoming major release Monkey v1.6 that will be the base too for Duda I/O stable branches dst-2 (dst-1 is based on 1.4), there is a new feature named "Overcapacity", it basically address the following scenario (example):
- Your server or web service is configured to handle up to 1000 concurrent connections (all of them opened at the same time). - You get 1200 concurrent connections. The behavior for this situation is very important as it may address different requirements of business needs, so the Overcapacity feature have 3 modes: 1) Drop : just drop any new incoming connection. 2) Resist : try to serve all request, even some of them may delay. 3) TooBusy: report a 503 Service Unavailable HTTP status. This is real world scenario where sadly no one of other Web Servers have some setup for this, just a hard coded action, personally i will make some noise about this as they should implement it. But for our case i would like to ask for your comments based in your experience using web servers, at the moment the development version have by default a "Resist" mode, but i would like to collect additional opinions. Also if you had deal with this before and want to add some comments, you are welcome. note: even this feature may sound more interesting for high-end production servers, think in an Embedded device that is configured to attend a concurrency of 50 and it get 100. The case apply for any kind of HW and environment. best regards, -- Eduardo Silva http://edsiper.linuxchile.cl http://monkey-project.com _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
