X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9456B568B4 for ; Tue, 15 Mar 2005 16:21:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92831-02 for ; Tue, 15 Mar 2005 16:21:56 +0000 (GMT) Received: from mail.eulerhermes.pl (mail.hermes-kredit.pl [217.153.119.83]) by svr1.postgresql.org (Postfix) with ESMTP id 4E36556409 for ; Tue, 15 Mar 2005 16:21:55 +0000 (GMT) Received: from [192.168.49.9] (helo=xterm.podsiec) by mail.eulerhermes.pl with esmtpa (Exim 4.42) id 1DBEeC-0002es-2i for pgsql-admin@postgresql.org; Tue, 15 Mar 2005 17:11:56 +0100 From: Marcin Giedz Organization: Euler Hermes To: pgsql-admin@postgresql.org Subject: Re: Performance problem... Date: Tue, 15 Mar 2005 17:17:36 +0100 User-Agent: KMail/1.7.1 References: <200503141903.08793.marcin.giedz@eulerhermes.pl> <200503150959.39708.marcin.giedz@eulerhermes.pl> <1110902907.28555.126.camel@state.g2switchworks.com> In-Reply-To: <1110902907.28555.126.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200503151717.36288.marcin.giedz@eulerhermes.pl> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.141 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/228 X-Sequence-Number: 16726 Dnia wtorek, 15 marca 2005 17:08, Scott Marlowe napisa=C5=82: > On Tue, 2005-03-15 at 02:59, Marcin Giedz wrote: > > Dnia poniedzia=C5=82ek, 14 marca 2005 19:32, Scott Marlowe napisa=C5=82: > > > On Mon, 2005-03-14 at 12:03, Marcin Giedz wrote: > > > > Hello... > > > > > > > > > > > > Our company is going to change SQL engine from MySQL to PSQL. Of > > > > course some performance problems occured. Our server is Dual Xeon > > > > 3.0GHz + 8GB RAM + RAID1(software - two 146GB SCSI 15k) for sql data > > > > + RAID1(software - two 146GB SCSI 15k) for pg_xlog. Postgres.conf > > > > parameters are as follows: > > > > > > > > max_connections =3D 150 > > > > shared_buffers =3D 50000 # min 16, at least max_connection= s*2, > > > > 8KB each work_mem =3D 2048 # min 64, size in KB > > > > > > 50,000 shared buffers may or may not be too much. Try it at different > > > sizes from 5,000 or so up to 50,000 and find the "knee". It's usually > > > closer to 10,000 than 50,000, but ymmv... > > > > Playing with shared_buffers from 10000 to 50000 doesn't change anything > > in total time for this query :( But when I change work_mem a little > > higher to 10000 total runtime decreases a little about 10% but when I > > change random_page_cost to 0.2 (I know that almost all papers say it > > should be higher then 1.0) total runtime decreases almost 3 times and > > lasts about 900ms - earlier with random_page_cost=3D1.2 it took 2.7s. I= s it > > possible to have random_page_cost on this value? > > IF random_page_cost needs to be that low, then it's likely that the > query planner is either getting bad statistics and making a poor > decision, or that you've got a corner case that it just can't figure > out. What does explain analyze say with > random_page_cost set to 1.2 and 0.2? HAve you run analyze and vacuumed > full lately? It cann't be possible - I've run vacuum full analyze - it didn't change=20 anything ;) Marcin