| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgres crashes on insert in 40 different threads |
| Date: | 2013-08-25 15:33:42 |
| Message-ID: | 9A8460E0-A087-4002-8153-A7A295C45E4D@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Aug 25, 2013, at 2:04 AM, Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> 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(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed Tarento | 2013-08-26 03:10:29 | Root partition full of files in /var/lib/postgresql/9.1/main/pg_xlog |
| Previous Message | Dzmitry | 2013-08-25 08:04:57 | Re: postgres crashes on insert in 40 different threads |