Database pool size for threading

NEWS.md

@@ -8,7 +8,8 @@
   2. Configure metadata api credentials and timeout. Take a look at `org_metadata_api` inside `config/app_config.yml.sample`.
   3. Trigger configuration: `RAILS_ENV=development bundle exec rake cartodb:db:configure_extension_org_metadata_api_endpoint`.
   4. Trigger org owner role assignment: `RAILS_ENV=development bundle exec rake cartodb:db:assign_org_owner_role`.
-  5. From now on you must run the server in multithread mode: `bundle exec thin start --threaded -p 3000 --threadpool-size 5`.
+  5. Increase your database pool size to 50 (5 x # threads, see next line) at config/database.yml. Sample development configuration: config/database.yml.sample
+  6. From now on you must run the server in multithread mode: `bundle exec thin start --threaded -p 3000 --threadpool-size 5`.
 * StatsD data gathering refactored. Check /lib/cartodb/stats for details
 * Data library feature is not cartodb user dependent anymore. By default the username you defined in the common-data config section, will be used with your base url to query for public datasets to build your own data-library based on that user. You can define the `base_url` property and point to other domain to retreive the public datasets from that user. For example set to `https://common-data.cartodb.com` you are going to keep using the cartodb data-library. Please refer to the example configuration file (app_config.yml.sample) `common_data`section  to check how it could be configured
 * New modals (removing old code & feature flag restricting access to new ones) [#5068](https://github.com/CartoDB/cartodb/pull/5068)

config/database.yml.sample

@@ -27,6 +27,7 @@ development:
   username: postgres
   password:
   conn_validator_timeout: 900
+  pool: 50
 
 test:
   adapter: postgres