X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2AFE69DC829 for ; Wed, 25 Jan 2006 14:04:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34458-08 for ; Wed, 25 Jan 2006 14:04:22 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by postgresql.org (Postfix) with ESMTP id 925139DC984 for ; Wed, 25 Jan 2006 14:04:20 -0400 (AST) Received: by zproxy.gmail.com with SMTP id 14so162890nzn for ; Wed, 25 Jan 2006 10:04:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=HbCfUy961iMs58lhP+GisRfstucStFuxiiek0ve1BApsQlIYp+MFX8trNAXhVpwZRFQzjM2uqn6WefmKP+K32SYkVHIxUsCB+RFjUL+5qPZDLVRN5Xb78UKbdWeXq6awACWf6uBZsCHq7cvAiwiMo3pL/aefxSkYMwj9Cy41VRA= Received: by 10.64.148.14 with SMTP id v14mr514944qbd; Wed, 25 Jan 2006 10:03:47 -0800 (PST) Received: by 10.64.53.18 with HTTP; Wed, 25 Jan 2006 10:03:47 -0800 (PST) Message-ID: <45dd8dbe0601251003w66cf12c0u4954bca165fb75e2@mail.gmail.com> Date: Wed, 25 Jan 2006 15:03:47 -0300 From: Dario Brignardello To: arnaulist@andromeiberica.com Subject: Re: Where is my bottleneck? Cc: pgsql-admin@postgresql.org, John Jensen In-Reply-To: <43D7ADE3.1050803@andromeiberica.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_60775_26879576.1138212227452" References: <43D7ADE3.1050803@andromeiberica.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.06 required=5 tests=[AWL=0.059, HTML_MESSAGE=0.001] X-Spam-Score: 0.06 X-Spam-Level: X-Archive-Number: 200601/286 X-Sequence-Number: 20374 ------=_Part_60775_26879576.1138212227452 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Arnu, > > The parameters related with memory usage of postgresql.conf all are the > default values (I haven't changed any value in the postgresql.conf file) Well, there is actually plenty of room to optimize there, I would suggest t= o go to http://www.postgresql.org/docs/7.4/interactive/runtime-config.html#RUNTIME-= CONFIG-RESOURCE and take a look, specially the values for shared_buffers and sort_mem shoul= d be higher (mind you, you also have to tune your kernel parameters or your engine will not start, so be careful :-) ) > I know that I can tune my queries, but I think I could get more >performance from the hardware I have. Actually you can, but a bad query is always a bad query, even when runing on big iron, so you should be sure you are not wasting hw resources, specially if those are scarce :-) > My settings are, do I should change anything else? > > # - Query/Index Statistics Collector - > stats_start_collector =3D true > stats_command_string =3D true > #stats_block_level =3D false > stats_row_level =3D true > #stats_reset_on_server_start =3D true Take a look at the pg_stat_* views, to see what could be out off the way. T= o an explanation of the statistics views, check: http://www.postgresql.org/docs/7.4/interactive/monitoring-stats.html Hope it helps. Best regards Dario -- Atte: Dario Brignardello ------=_Part_60775_26879576.1138212227452 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Arnu,


>
> The parameters related with memory usage= of postgresql.conf all are the
> default values (I haven't changed a= ny value in the postgresql.conf file)

Well, there is actually plenty= of room to optimize there, I would suggest to go to  =20
http://www.postgresql.org/docs/7.4/interact= ive/runtime-config.html#RUNTIME-CONFIG-RESOURCE

and take a look, specially the values for shared_buffers and so= rt_mem should be higher (mind you, you also have to tune your kernel parame= ters or your engine will not start, so be careful :-) )
 

= >   I know that I can tune my queries, but I think I could get= more
>performance from the hardware I have.

Actually you can, but = a bad query is always a bad query, even when runing on&= nbsp;big iron, so you should be sure you= are not wasting hw resources, specially if those are scarce= :-)


> My settings are, do I should change anything else?
>=
> # - Query/Index Statistics Collector -

> stats_start_col= lector =3D true
> stats_command_string =3D true
> #stats_block_= level =3D false
> stats_row_level =3D true
> #stats_reset_on_server_start =3D= true

Take a look at the pg_stat_* views, to see what = ;could be out off the way. To an explanation of th= e statistics views, check:
http://www.postgresql.org/docs/7.4/interactive/monitoring-stats.html
Hope it helps.
Best regards
Dario


--
Atte: Dario= Brignardello

------=_Part_60775_26879576.1138212227452--