Re: Peformance Tuning Opterons/ Hard Disk Layout - Mailing list pgsql-performance

From Tom Lane
Subject Re: Peformance Tuning Opterons/ Hard Disk Layout
Date
Msg-id 21021.1109183848@sss.pgh.pa.us
Whole thread Raw
In response to Re: Peformance Tuning Opterons/ Hard Disk Layout  ("Bruno Almeida do Lago" <teolupus@gmail.com>)
Responses Re: Peformance Tuning Opterons/ Hard Disk Layout  (John Allgood <john@turbocorp.com>)
Re: Peformance Tuning Opterons/ Hard Disk Layout  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-performance
"Bruno Almeida do Lago" <teolupus@gmail.com> writes:
> Is there a real limit for max_connections? Here we've an Oracle server with
> up to 1200 simultaneous conections over it!

[ shrug... ] If your machine has the beef to run 1200 simultaneous
queries, you can set max_connections to 1200.

The point of what you were quoting is that if you want to service
1200 concurrent users but you only expect maybe 100 simultaneously
active queries from them (and you have a database box that can only
service that many) then you want to put a connection pooler in
front of 100 backends, not try to start a backend for every user.

Oracle may handle this sort of thing differently, I dunno.

            regards, tom lane

pgsql-performance by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout
Next
From: Tom Lane
Date:
Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout