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 EA05A53398 for ; Mon, 4 Apr 2005 20:13:57 +0100 (BST) 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 27804-06 for ; Mon, 4 Apr 2005 19:13:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by svr1.postgresql.org (Postfix) with ESMTP id 24BCE52A5C for ; Mon, 4 Apr 2005 20:13:48 +0100 (BST) Received: by wproxy.gmail.com with SMTP id 68so1674887wri for ; Mon, 04 Apr 2005 12:13:50 -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:references; b=lHaJhhLQv3pgC6PKEKKctB4PUcTBEPt7gWsKM6PdvcC0YiUo1EyhYHYpBulLQCwQ7UJAwaOIoUcOeQMXrKrCOZU2qwzGaU7S6M4/8RqF8jkCv8Vh30sMEvSUF68DK9ujBVGLIsl9OMxprNNLrf4f5CEdQuB2PBof9IvOkRbZ0vg= Received: by 10.54.13.34 with SMTP id 34mr260wrm; Mon, 04 Apr 2005 12:12:54 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 4 Apr 2005 12:12:20 -0700 (PDT) Message-ID: <33c6269f05040412126b5bc719@mail.gmail.com> Date: Mon, 4 Apr 2005 15:12:20 -0400 From: Alex Turner Reply-To: Alex Turner To: Steve Poe Subject: Re: How to improve db performance with $7K? Cc: pg@fastcrypt.com, pgsql-performance@postgresql.org In-Reply-To: <42515198.9090903@sfnet.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <42443863.4040302@sfnet.cc> <42453273.2060509@turtle-entertainment.de> <200503261255.59007.josh@agliodbs.com> <42455DEC.2080301@sfnet.cc> <1112049794.23284.29.camel@localhost.localdomain> <424840AE.3050200@sfnet.cc> <42494741.7060806@fastcrypt.com> <33c6269f0504040643317b69cd@mail.gmail.com> <42515198.9090903@sfnet.cc> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.247 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/59 X-Sequence-Number: 11456 I'm no drive expert, but it seems to me that our write performance is excellent. I think what most are concerned about is OLTP where you are doing heavy write _and_ heavy read performance at the same time. Our system is mostly read during the day, but we do a full system update everynight that is all writes, and it's very fast compared to the smaller SCSI system we moved off of. Nearly a 6x spead improvement, as fast as 900 rows/sec with a 48 byte record, one row per transaction. I don't know enough about how SATA works to really comment on it's performance as a protocol compared with SCSI. If anyone has a usefull link on that, it would be greatly appreciated. More drives will give more throughput/sec, but not necesarily more transactions/sec. For that you will need more RAM on the controler, and defaintely a BBU to keep your data safe. Alex Turner netEconomist On Apr 4, 2005 10:39 AM, Steve Poe wrote: > > > Alex Turner wrote: > > >To be honest, I've yet to run across a SCSI configuration that can > >touch the 3ware SATA controllers. I have yet to see one top 80MB/sec, > >let alone 180MB/sec read or write, which is why we moved _away_ from > >SCSI. I've seen Compaq, Dell and LSI controllers all do pathetically > >badly on RAID 1, RAID 5 and RAID 10. > > > > > Alex, > > How does the 3ware controller do in heavy writes back to the database? > It may have been Josh, but someone said that SATA does well with reads > but not writes. Would not equal amount of SCSI drives outperform SATA? > I don't want to start a "whose better" war, I am just trying to learn > here. It would seem the more drives you could place in a RAID > configuration, the performance would increase. > > Steve Poe > >