Clay Gerrard de3acec4bf Set default wsgi workers to cpu_count ... Change the default value of wsgi workers from 1 to auto. The new default value for workers in the proxy, container, account & object wsgi servers will spawn as many workers per process as you have cpu cores. This will not be ideal for some configurations, but it's much more likely to produce a successful out of the box deployment. Inspect the number of cpu_cores using python's multiprocessing when available. Multiprocessing was added in python 2.6, but I know I've compiled python without it before on accident. The cpu_count method seems to be pretty system agnostic, but it says it can raise NotImplementedError or sometimes return 0. Add a new utility method 'config_auto_int_value' to pull an integer out of the config which has a dynamic default. * drive by s/container/proxy/ in proxy-server.conf.5 * fix misplaced max_clients in *-server.conf-sample * update doc/development_saio to force workers = 1 DocImpact Change-Id: Ifa563d22952c902ab8cbe1d339ba385413c54e95		2013-07-18 22:57:18 -07:00
..
functional	Fix functional tests with keystone.	2013-06-12 13:12:57 +02:00
functionalnosetests	Swift tests for unicode headers	2013-06-09 12:54:32 +03:00
probe	Fix faked-out account GET for JSON and XML.	2013-05-30 17:43:03 -07:00
unit	Set default wsgi workers to cpu_count	2013-07-18 22:57:18 -07:00
__init__.py	fixed some minor things in tests that pyflakes complained about	2013-03-26 20:42:26 +00:00
sample.conf	Permit functional tests against Swift with Keystone	2013-03-10 18:52:10 -06:00