Skip site navigation (1) Skip section navigation (2)

Re: Feature Request --- was: PostgreSQL Performance Tuning

From: Carlos Moreno <moreno_pg(at)mochima(dot)com>
To: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
Date: 2007-04-27 13:27:49
Message-ID: 4631FA55.4010406@mochima.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-performance
Tom Lane wrote:
> Carlos Moreno <moreno_pg(at)mochima(dot)com> writes:
>   
>> ...  But, wouldn't it make sense that the configure script
>> determines the amount of physical memory and perhaps even do a HD
>> speed estimate to set up defaults that are closer to a 
>> performance-optimized
>> configuration?
>>     
>
> No.  Most copies of Postgres these days are executed on machines very
> far away from where the code was built.  It's a little bit safer to
> try to tune things at initdb time ... as indeed we already do. 

D'oh!  Yes, that makes more sense, of course.

>  But
> the fundamental problem remains that we don't know that much about
> how the installation will be used. 

Notice that the second part of my suggestion covers this --- have 
additional
switches to initdb so that the user can tell it about estimates on how 
the DB
will be used:  estimated size of the DB, estimated percentage of 
activity that
will involve writing, estimated percentage of activity that will be 
transactions,
percentage that will use indexes, percentage of queries that will be 
complex,
etc. etc.

Wouldn't initdb be able to do a better job at coming up with sensible
defaults if it counts on this information?   Of course, all these 
parameters
would have their own defaults --- the user won't necessarily know or have
an accurate estimate for each and every one of them.

> Also, there is an extremely good reason why Postgres will never be set
> up to try to take over the whole machine by default: most of the
> developers run multiple postmasters on their machines.
>   
Wouldn't this be covered by the above suggestion??  One of the switches
for the command initdb could allow the user to specify how many instances
will be run  (I assume you're talking about having different instances 
listening
on different ports for increased concurrency-related benefits?)

Does my suggestion make more sense now?  Or is it still too unrealistic to
make it work properly/safely?

Carlos
--


In response to

Responses

pgsql-performance by date

Next:From: Jim NasbyDate: 2007-04-27 14:08:50
Subject: Re: What`s wrong with JFS configuration?
Previous:From: Michael StoneDate: 2007-04-27 12:52:45
Subject: Re: Usage up to 50% CPU

pgsql-general by date

Next:From: Rich ShepardDate: 2007-04-27 13:36:37
Subject: Preferred Installation/Data Directories
Previous:From: Alvaro HerreraDate: 2007-04-27 13:18:08
Subject: Re: Vacuum-full very slow

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group