| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> |
| Cc: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgres crashes on insert in 40 different threads |
| Date: | 2013-08-19 15:17:22 |
| Message-ID: | ED6CA3D8-8424-4069-A6D7-A9473D9F569F@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Aug 19, 2013, at 9:07 AM, Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> wrote:
> Yes- I need so many threads...
This is not at all clear from your answer. At most, 1 thread per logical core can execute at any one time. And while many can be waiting on IO instead of executing, there is still a rather low limit to how many threads it takes to saturate IO capacity. If you actually tried to *run* 550 processes at the same time, you'd just be wasting time on contention.
So, back to the question I just asked a minute ago in the prior email, do you have any idea how many pg connections are actually being used?
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dzmitry | 2013-08-19 15:21:43 | Re: postgres crashes on insert in 40 different threads |
| Previous Message | Dzmitry | 2013-08-19 15:07:48 | Re: postgres crashes on insert in 40 different threads |