From: | Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(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:21:43 |
Message-ID: | CE381213.119DA%dzmitry.nikitsin@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry for confusion.
I have 2 machines, each machine run 1 process, with 20 threads in each -
total 40 threads. Every thread connected to postgres and insert data. I am
using technology, that keep connection opens. It means every thread open 1
connection when it starts, and will closed it - only when killed. But
threads performing background jobs - it means they running always, so I
keep connection always open.
Thanks,
Dzmitry
On 8/19/13 6:17 PM, "Scott Ribe" <scott_ribe(at)elevated-dev(dot)com> wrote:
>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 | Scott Ribe | 2013-08-19 15:25:35 | Re: postgres crashes on insert in 40 different threads |
Previous Message | Scott Ribe | 2013-08-19 15:17:22 | Re: postgres crashes on insert in 40 different threads |