Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Configuration Issue ?
Date: Wed, 25 Oct 2006 16:57:09 -0400
Message-ID: <673ECBB77DA91F47AD4902A5FD73BCE4BA3A94@mail3>
Thread-Topic: [PERFORM] Configuration Issue ?
Thread-Index: Acb4d33XO855bkitTCSdN7Qe5BMXfQAAGjkg
From: "Mark Lonsdale" <mark.lonsdale@wysdm.com>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: <pgsql-performance@postgresql.org>


Hi Josh

Thanks for the feedback, that is most usefull.  When you said one of the
settings was likely killing us, was it all of the settings for
max_fsm_relations, max_fsm_pages, and sort_mem or just the setting for
sort_mem ?

Can you explain why the setting would be killing me :-)

Thanks

Mark

-----Original Message-----
From: Joshua D. Drake [mailto:jd@commandprompt.com]=20
Sent: 25 October 2006 21:52
To: Mark Lonsdale
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Configuration Issue ?

Mark Lonsdale wrote:
> =20
>=20
> Hi=20
>=20
> =20
>=20
> Please help.  I have got a postgres 7.3.4 database running on RedHat
ES
> 3, with 8GB of physical memory in it.   The machine is shared with my
> application which is pretty intensive in doing selects and updates
> against the database, but there are usually no more than 10
connections
> to the database at any time.
>=20
>=20
> shared_buffers =3D 393216         # min max_connections*2 or 16, 8KB
each

The above is likely hurting you more than helping you with 7.3.

>=20
> max_fsm_relations =3D 10000       # min 10, fsm is free space map, ~40
> bytes
>=20
> max_fsm_pages =3D 160001          # min 1000, fsm is free space map, =
~6
>=20
> bytes
>=20
> sort_mem =3D 409600               # min 64, size in KB

The above will likely kill you :). Try 4096 or 8192, maybe 16384
depending on workload.

>=20
> vacuum_mem =3D 81920              # min 1024, size in KB

This is fine.

>=20
> Also if you have any recommendations regarding effective_cache_size Id
> be interested as reading around this sounds important as well

About 20-25% of available ram for 7.3.


The long and short is you need to upgrade to at least 7.4, preferrably
8.1.

Joshua D. Drake


>=20
> =20
>=20
> Thanks
>=20
> =20
>=20
> Mark=20
>=20
> =20
>=20
>=20


--=20

      =3D=3D=3D The PostgreSQL Company: Command Prompt, Inc. =3D=3D=3D
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate