pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Offering tuned config files
4+ messages / 3 participants
[nested] [flat]

* Offering tuned config files
@ 2003-02-14 06:12  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 1 reply; 4+ messages in thread

From: Christopher Kings-Lynne @ 2003-02-14 06:12 UTC (permalink / raw)
  To: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>

OK,

Here's a stab at some extra conf files.  Feel free to shoot them down.

If we can come up with at least _some_ alternative files that we can put
somewhere for them to see when postgres is installed, then at least people
can see what variables will affect what...

I didn't see the point of a 'workstation' option, the default is fine for
that.

Chris


> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Kevin Brown
> Sent: Friday, 14 February 2003 11:26 AM
> To: PostgresSQL Hackers Mailing List; pgsql-advocacy@postgresql.org
> Subject: Re: [HACKERS] Changing the default configuration (was Re:
> [pgsql-advocacy]
>
>
> Josh Berkus wrote:
> > > > Uh ... do we have a basis for recommending any particular sets of
> > > > parameters for these different scenarios?  This could be a good idea
> > > > in the abstract, but I'm not sure I know enough to fill in
> the details.
> >
> > Sure.
> > Mostly-Read database, few users, good hardware, complex queries:
> > 	= High shared buffers and sort mem, high geqo and join
> collapse thresholds,
> > 		moderate fsm settings, defaults for WAL.
> > Same as above with many users and simple queries (webserver) =
> > 	same as above, except lower sort mem and higher connection limit
> > High-Transaction Database =
> > 	Moderate shared buffers and sort mem, high FSM settings,
> increase WAL files
> > and buffers.
> > Workstation =
> > 	Moderate to low shared buffers and sort mem, moderate FSM,
> defaults for WAL,
> > etc.
> > Low-Impact server = current defaults, more or less.
>
> Okay, but there should probably be one more, called "Benchmark".  The
> real problem is what values to use for it.  :-)
>
>
>
> --
> Kevin Brown					      kevin@sysexperts.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>

Attachments:

  postgresql.conf.sample-olap (application/octet-stream, 5.5K) download

  postgresql.conf.sample-web (application/octet-stream, 5.3K) download

  postgresql.conf.sample-writeheavy (application/octet-stream, 5.2K) download

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Offering tuned config files
@ 2003-02-14 11:58  Manfred Koizar <mkoi-pg@aon.at>
  parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  0 siblings, 1 reply; 4+ messages in thread

From: Manfred Koizar @ 2003-02-14 11:58 UTC (permalink / raw)
  To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>

On Fri, 14 Feb 2003 14:12:50 +0800, "Christopher Kings-Lynne"
<chriskl@familyhealth.com.au> wrote:
>Here's a stab at some extra conf files.  Feel free to shoot them down.

No intent to shoot anything down, just random thoughts:

effective_cache_size = 20000 (~ 160 MB) should be more adequate for a
256 MB machine than the extremely conservative default of 1000.  I
admit that the effect of this change is hard to benchmark.  A way too
low (or too high) setting may lead the planner to wrong conclusions.

More parameters affecting the planner:
	#cpu_tuple_cost = 0.01
	#cpu_index_tuple_cost = 0.001
	#cpu_operator_cost = 0.0025

Are these still good defaults?  I have no hard facts, but ISTM that
CPU speed is increasing more rapidly than disk access speed.

In postgresql.conf.sample-writeheavy you have:
	commit_delay = 10000

Is this still needed with "ganged WAL writes"?  Tom?

Servus
 Manfred



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Offering tuned config files
@ 2003-02-14 15:07  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Manfred Koizar <mkoi-pg@aon.at>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2003-02-14 15:07 UTC (permalink / raw)
  To: Manfred Koizar <mkoi-pg@aon.at>; +Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>

Manfred Koizar <mkoi-pg@aon.at> writes:
> In postgresql.conf.sample-writeheavy you have:
> 	commit_delay = 10000
> Is this still needed with "ganged WAL writes"?  Tom?

I doubt that the current options for grouped commits are worth anything
at the moment.  Chris, do you have any evidence backing up using
commit_delay with 7.3?

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Offering tuned config files
@ 2003-02-15 14:15  Christopher Kings-Lynne <chriskl@familyhealth.com.au>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Christopher Kings-Lynne @ 2003-02-15 14:15 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Manfred Koizar <mkoi-pg@aon.at>; PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>

No, not really - I can do some more testing with pgbench to see what
happens though...I'll do it on monday

Chris

On Fri, 14 Feb 2003, Tom Lane wrote:

> Manfred Koizar <mkoi-pg@aon.at> writes:
> > In postgresql.conf.sample-writeheavy you have:
> > 	commit_delay = 10000
> > Is this still needed with "ganged WAL writes"?  Tom?
>
> I doubt that the current options for grouped commits are worth anything
> at the moment.  Chris, do you have any evidence backing up using
> commit_delay with 7.3?
>
> 			regards, tom lane
>




^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2003-02-15 14:15 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-02-14 06:12 Offering tuned config files Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2003-02-14 11:58 ` Manfred Koizar <mkoi-pg@aon.at>
2003-02-14 15:07   ` Tom Lane <tgl@sss.pgh.pa.us>
2003-02-15 14:15     ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox