hi,
Paul Serby wrote:
Can anyone give a good reference site/book for getting the most out of
your postgres server.
All I can find is contradicting theories on how to work out your settings.
This is what I followed to setup our db server that serves our web
applications.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks to everyone for there help.
I've changed my postgres settings to the following
max_connections = 500
shared_buffers = 1
sort_mem = 2000
effective_cache_size = 5000
The 'effective_cache_size' is just a guess, but some references suggest
it so
On Monday 09 Aug 2004 7:58 pm, Paul Serby wrote:
I've not maxed out the connections since making the changes, but I'm
still not convinced everything is running as well as it could be. I've
got some big result sets that need sorting and I'm sure I could spare a
bit more sort memory.
You could
Paul Serby wrote:
Can anyone give a good reference site/book for getting the most out of
your postgres server.
All I can find is contradicting theories on how to work out your settings.
This is what I followed to setup our db server that serves our web
applications.
Paul,
Physical Memory: 2077264 kB
sort_mem = 12000
Hmmm. Someone may already have mentioned this, but that looks problematic.
You're allowing up to 12MB per sort, and up to 300 connections. Even if each
concurrent connection averages only one sort (and they can use more) that's
3600MB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Berkus wrote:
| Paul,
|
|
|Physical Memory: 2077264 kB
|
|
|sort_mem = 12000
|
|
| Hmmm. Someone may already have mentioned this, but that looks problematic.
| You're allowing up to 12MB per sort, and up to 300 connections. Even if each
|
Gaetano,
Of course your are speaking about the worst case, I aplly in scenarios
like
this on the rule 80/20: 80% of connection will perform a sort and 20% will
allocate
memory for the sort operation in the same window time:
Well, I suppose it depends on how aggresive your connection pooling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Berkus wrote:
| Gaetano,
|
|
|Of course your are speaking about the worst case, I aplly in scenarios
|
| like
|
|this on the rule 80/20: 80% of connection will perform a sort and 20% will
|
| allocate
|
|memory for the sort operation in the same
On Aug 4, 2004, at 8:45 AM, Paul Serby wrote:
Apache on the Web server can take up to 300 connections and PHP is
using pg_pconnect
Postgres is set with the following.
max_connections = 300
shared_buffers = 38400
sort_mem = 12000
But Apache is still maxing out the non-super user connection
Paul Serby wrote:
Apache on the Web server can take up to 300 connections and PHP is using
pg_pconnect
max_connections = 300
But Apache is still maxing out the non-super user connection limit.
Don't forget also that some connections are reserved for superusers
(usually 2), so if you want 300
Am Mittwoch, 4. August 2004 14:45 schrieb Paul Serby:
Apache on the Web server can take up to 300 connections and PHP is using
pg_pconnect
Postgres is set with the following.
max_connections = 300
shared_buffers = 38400
sort_mem = 12000
But Apache is still maxing out the non-super user
On 04/08/2004 13:45 Paul Serby wrote:
Can anyone give a good reference site/book for getting the most out of
your postgres server.
All I can find is contradicting theories on how to work out your
settings.
This is what I followed to setup our db server that serves our web
applications.
12 matches
Mail list logo
