On Aug 25, 2013, at 2:04 AM, Dzmitry <dzmitry.nikitsin@xxxxxxxxx> wrote: > Ok,thank you, it's a good point. Need to review & make fixes with what I > have. Yes, as suggested I would try just reducing first. Where connection pooling could help is if your load across all those rails apps is not spread out evenly, but varies over time such that there is *no* single small number of workers that is right for all conditions. Because the same comments about no benefit from tons of threads applies to the pg server as well: so 110 connections simultaneously doing work is not likely to be better than some smaller number... -- Scott Ribe scott_ribe@xxxxxxxxxxxxxxxx http://www.elevated-dev.com/ (303) 722-0567 voice -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
