On 11.10.12 20:28, Gustaf Neumann wrote: > So, the behavior should be at least parameterized, and tailorable. > i have added a proposal to hg, which is just a few lines of code, > that allows parallel thread creation above a certain threshold. > the threshold should become a parameter. If the threshold > is set large enough, the thread serialization happens, if it is > small, parallel thread creates are allowed. Ideas for a > good name of the parameter are very welcome. i have made not the concurrent creation of connection threads configurable, but not via an absolute value as in the first shot, but as a percentage, how full the requests queue is to allow concurrent creates. The same parameter can be used to allow always parallel connection thread creates or to disallow it in general. For more details, see
https://bitbucket.org/naviserver/naviserver/changeset/76c070ff3311babfa272cec7d086ee4f03c09f9e A suggestion for better and shorter name is welcome. -gustaf neumann ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
