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 472D6535C2 for ; Mon, 18 Apr 2005 13:56:51 -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 84865-09 for ; Mon, 18 Apr 2005 16:56:50 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by svr1.postgresql.org (Postfix) with ESMTP id A41785359B for ; Mon, 18 Apr 2005 13:56:48 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so1518550wri for ; Mon, 18 Apr 2005 09:56: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=esJv6lT7jOWzufw8tfOlQZ1v/B3tWTvohCe4mvo7U6ckK/qf5e7zW7ZP0pNtRC80WDW9KRMDCDhrVa5jNt1h31Bklb5UagLwBATsLN+UbM5iMd0vhfxVYwR0r+58KrLa3mntaDoPelxRfy0Zw89KwNl8YAkNWeJMO2MKrAxxl7E= Received: by 10.54.69.3 with SMTP id r3mr1477329wra; Mon, 18 Apr 2005 09:56:49 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 18 Apr 2005 09:56:48 -0700 (PDT) Message-ID: <33c6269f05041809566abf91d2@mail.gmail.com> Date: Mon, 18 Apr 2005 12:56:48 -0400 From: Alex Turner Reply-To: Alex Turner To: Greg Stark Subject: Re: How to improve db performance with $7K? Cc: William Yu , pgsql-performance@postgresql.org In-Reply-To: <878y3gks3p.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <425EBA0C.6030804@sfnet.cc> <87pswsku6e.fsf@stark.xeocode.com> <33c6269f0504180817511b27a3@mail.gmail.com> <878y3gks3p.fsf@stark.xeocode.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.275 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/409 X-Sequence-Number: 11806 [snip] >=20 > Adding drives will not let you get lower response times than the average = seek > time on your drives*. But it will let you reach that response time more o= ften. >=20 [snip] I believe your assertion is fundamentaly flawed. Adding more drives will not let you reach that response time more often. All drives are required to fill every request in all RAID levels (except possibly 0+1, but that isn't used for enterprise applicaitons). Most requests in OLTP require most of the request time to seek, not to read. Only in single large block data transfers will you get any benefit from adding more drives, which is atypical in most database applications.=20 For most database applications, the only way to increase transactions/sec is to decrease request service time, which is generaly achieved with better seek times or a better controller card, or possibly spreading your database accross multiple tablespaces on seperate paritions. My assertion therefore is that simply adding more drives to an already competent* configuration is about as likely to increase your database effectiveness as swiss cheese is to make your car run faster. Alex Turner netEconomist *Assertion here is that the DBA didn't simply configure all tables and xlog on a single 7200 RPM disk, but has seperate physical drives for xlog and tablespace at least on 10k drives.