X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4B1A0D1B8E7 for ; Wed, 27 Aug 2003 11:37:58 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 18708-09 for ; Wed, 27 Aug 2003 11:37:31 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id 17795D1B95A for ; Wed, 27 Aug 2003 11:37:26 -0300 (ADT) Received: (qmail 16948 invoked from network); 27 Aug 2003 14:37:14 -0000 Received: from dsl-217-155-239-50.zen.co.uk (217.155.239.50) by wight.ymogen.net with SMTP; 27 Aug 2003 14:37:14 -0000 Subject: Re: Hardware recommendations to scale to silly load From: matt To: Bill Moran Cc: pgsql-performance@postgresql.org In-Reply-To: <3F4CBD8A.4050309@potentialtech.com> References: <1061948112.15800.53.camel@gibraltar.mattclark.net> <3F4C1364.6080602@potentialtech.com> <1061990263.15800.124.camel@gibraltar.mattclark.net> <3F4CBD8A.4050309@potentialtech.com> Content-Type: text/plain Organization: Message-Id: <1061995033.15800.138.camel@gibraltar.mattclark.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 27 Aug 2003 15:37:14 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/364 X-Sequence-Number: 3180 > Don't know how "cheap" they are. > > I have an app that does large batch updates. I found that if I dropped > the indexes, did the updates and recreated the indexes, it was faster > than doing the updates while the indexes were intact. Yeah, unfortunately it's not batch work, but real time financial work. If I drop all the indexes my select performance goes through the floor, as you'd expect. > Does noatime make much difference on a PostgreSQL database? I haven't > tested that yet. Yup, it does. In fact it should probably be in the standard install documentation (unless someone has a reason why it shouldn't). Who *cares* when PG last looked at the tables? If 'nomtime' was available that would probably be a good thing too. > Can you split it onto multiple boxes? Some database layouts lend themselves > to this, others don't. Obviously you can't do joins from one server to > another, so you may lose more in multiple queries than you gain by having > multiple servers. It's worth looking into though. I'm considering that. There are some tables which I might be able to split out. There amy even be some things I can pull from the DB altogether (session info in particular, so long as I can reliably send a given user's requests to the same app server each time, bearing in mind I can't see the cookies too easily because 50% of the requests are over SSL) > I know my answers aren't quite the ones you were looking for, but my > experience is that many people try to solve poor application design > by simply throwing bigger hardware at the problem. It appears as though > you've already done your homework, though. Well, I *hope* that's the case! The core issue is simply that we have to deal with an insane load for 1 hour a week, and there's just no avoiding it. Maybe I can get Sun/HP/IBM to lend some gear (it's a pretty high-profile site).