On Wed, Aug 6, 2008 at 1:34 PM, Jorge Medina <[EMAIL PROTECTED]> wrote: > On Wed, Aug 6, 2008 at 1:38 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote: >> On Wed, Aug 6, 2008 at 11:29 AM, Jorge Medina <[EMAIL PROTECTED]> wrote: >>> On Wed, Aug 6, 2008 at 12:47 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote: >>>> On Wed, Aug 6, 2008 at 10:42 AM, Jorge Medina <[EMAIL PROTECTED]> wrote: >>>>>> >>>>> I have many trouble's with server, because my webmail(roundcube) works >>>>> with the db and the machine only have 2G of RAM but collapse with 60 >>>>> concurrent connections, I try with persistent connections and the same >>>>> problem, I need configure a pool of connection or something. >>>>> my config >>>>> max_connections = 100; >>>>> shared_buffer = 32MB >>>>> increase to 460 connections and 128MB of shared buffers but it's the same >>>> >>>> What, exactly, are the symptoms of a collapse? What do the logs >>>> (pgsql, system, your application) have to say? >>>> >>> affect directly the performance >> >> I'm trying to help you here, but that answer helps no one. >> > I know, sorry but the logs don't show anything when many people try > login from the webmail begin to grow connections to postgresql and the > all system turn too slow.
I'm not trying to be difficult, but there's a huge difference between the system slowing down a bit, slowing down a lot, slowing down to a crawl, and actually collapsing (failing to respond.) Are you running out of available connections? Do you have a lot that are idle? Do you run the machine out of memory? What are the symptoms of your failure? -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
