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 17:31:29 -0400
Message-ID: <673ECBB77DA91F47AD4902A5FD73BCE4BA3AC6@mail3>
Thread-Topic: [PERFORM] Configuration Issue ?
Thread-Index: Acb4ewHRw5cGeJhrRRqEzZaJLvOIbgAAPnEA
From: "Mark Lonsdale" <mark.lonsdale@wysdm.com>
To: "Joshua D. Drake" <jd@commandprompt.com>,
	"Richard Huxton" <dev@archonet.com>
Cc: <pgsql-performance@postgresql.org>


Thanks guys, I think we'll certainly look to get the app certified with
7.4 and 8.x but that may take a little while.   In the interim, Im
thinking of making the following changes then:-

Change Shared_buffers from 393216 to 80,000 ( ~15% of 4GB of RAM.
Server is 8GB but I want to leave space for App as well )

Set my effective_cache_size to 125,000 ( ~25% of 4GB of RAM )

Set my sort_mem to 8192

Do those numbers look a bit better?   Will probably see if we can make
these changes asap as the server is struggling a bit now, which doesn't
really make sense given how much memory is in it.

Really appreciate your help and fast turnaround on this

Mark

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

Richard Huxton wrote:
> Mark Lonsdale wrote:
>>
>> 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 :-)
>=20
> The sort_mem is crucial. It's memory *per sort*, which means one query
> can use several times that amount.

Worse then that it is:

((sort memory) * (number of sorts)) * (number of connections) =3D amount
of ram possible to use.

Now... take the following query:

SELECT * FROM foo
  JOIN bar on (bar.id =3D foo.id)
  JOIN baz on (baz.id =3D foo_baz.id)
ORDER BY baz.name, foo.salary;

Over 5 million rows... How much ram you think you just used?

>=20
>> The long and short is you need to upgrade to at least 7.4,
preferrably
>> 8.1.
>=20
> Joshua means this too. Upgrade to 7.3.16 within the next few days,
then
> test out something more recent. You should see some useful performance
> gains from 8.1.

Right. The reason I suggested 7.4 is that he gets VACUUM VERBOSE in a
reasonable fashion but of course 8.1 is better.

Sincerely,

Joshua D. Drake


>=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