X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 86415529F4 for ; Tue, 19 Jul 2005 15:42:54 -0300 (ADT) 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 76183-02 for ; Tue, 19 Jul 2005 18:42:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by svr1.postgresql.org (Postfix) with ESMTP id 183F6529C3 for ; Tue, 19 Jul 2005 15:42:48 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id i16so1281222wra for ; Tue, 19 Jul 2005 11:42:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r5DY2JxmIAD0Btdi9i6RSbxAUB6YePn70bDY2i8ZrcTkgLc7EZJtdmvuitTFmpiTmu+0KbE00lx4RRUZ8khIqFwl+uzaxsCKtLPaZ8L6QQYFt9oAx7Ph0a5qekGTe+2gSOaZYFj/2A3q5axspb6TihI/GytSgpuZWimYY/r0hic= Received: by 10.54.57.79 with SMTP id f79mr846368wra; Tue, 19 Jul 2005 11:41:51 -0700 (PDT) Received: by 10.54.150.2 with HTTP; Tue, 19 Jul 2005 11:41:51 -0700 (PDT) Message-ID: <1efd553a05071911413e50ea90@mail.gmail.com> Date: Tue, 19 Jul 2005 14:41:51 -0400 From: Oliver Crosby Reply-To: Oliver Crosby To: Richard Huxton Subject: Re: Looking for tips Cc: pgsql-performance@postgresql.org In-Reply-To: <42DD420C.2010306@archonet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1efd553a05071910427b290203@mail.gmail.com> <42DD420C.2010306@archonet.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.123 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200507/306 X-Sequence-Number: 13547 > Identify what the problem is first of all. Some things to consider: > - Are there particular queries giving you trouble? > - Is your load mostly reads or mostly writes? > - Do you have one user or 100? > - Are you block-loading data efficiently where necessary? > - Have you indexed both sides of your foreign-keys where sensible? > - Are your disks being used effectively? > - Are your statistics accurate/up to date? No queries in particular appear to be a problem. I think it's just the overall speed. If any of the configuration settings will help make the simple select queries go faster, that would be ideal. The load is about 50/50 read/write. At the moment it's just one user, but the goal is to have a cluster of servers (probably less than a dozen) updating to a central db. Indices exist for the fields being searched, but we don't have any foreign = keys. I'm not too familiar with effective disk usage or statistics...