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 0AE3D535C8 for ; Mon, 18 Apr 2005 14:46:52 -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 12798-03 for ; Mon, 18 Apr 2005 17:46:50 +0000 (GMT) Received: from mail.tecarta.com (66.238.115.135.ptr.us.xo.net [66.238.115.135]) by svr1.postgresql.org (Postfix) with ESMTP id 7A9FC535D8 for ; Mon, 18 Apr 2005 14:46:49 -0300 (ADT) Received: from mail pickup service by mail.tecarta.com with Microsoft SMTPSVC; Mon, 18 Apr 2005 10:49:49 -0700 Received: from mail.tecarta.com ([192.168.160.2]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 18 Apr 2005 10:49:48 -0700 Received: from barracuda.tecarta.com ([192.168.160.200]) by mail.tecarta.com (SAVSMTP 3.1.0.29) with SMTP id M2005041810494810305 for ; Mon, 18 Apr 2005 10:49:48 -0700 X-ASG-Debug-ID: 1113846405-32259-12-0 X-Barracuda-URL: http://192.168.160.200:8000/cgi-bin/mark.cgi Received: from mail1 (mail1.hq.corp [192.168.160.5]) by barracuda.tecarta.com (Spam Firewall) with SMTP id 05787202B608 for ; Mon, 18 Apr 2005 10:46:45 -0700 (PDT) Received: from [192.168.0.13] ([63.206.203.145]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 18 Apr 2005 10:49:43 -0700 Message-ID: <4263F259.7030804@sfnet.cc> Date: Mon, 18 Apr 2005 10:46:01 -0700 From: Steve Poe User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Turner Cc: pgsql-performance@postgresql.org X-ASG-Orig-Subj: Re: [PERFORM] How to improve db performance with $7K? Subject: Re: How to improve db performance with $7K? References: <425EBA0C.6030804@sfnet.cc> <87pswsku6e.fsf@stark.xeocode.com> <33c6269f0504180817511b27a3@mail.gmail.com> <878y3gks3p.fsf@stark.xeocode.com> <33c6269f05041809566abf91d2@mail.gmail.com> In-Reply-To: <33c6269f05041809566abf91d2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Apr 2005 17:49:43.0099 (UTC) FILETIME=[007170B0:01C5443F] X-Virus-Scanned: by Barracuda Spam Firewall at tecarta.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BAYES_50 X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.376 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.725 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, NO_DNS_FOR_FROM X-Spam-Level: X-Archive-Number: 200504/416 X-Sequence-Number: 11813 Alex, In the situation of the animal hospital server I oversee, their application is OLTP. Adding hard drives (6-8) does help performance. Benchmarks like pgbench and OSDB agree with it, but in reality users could not see noticeable change. However, moving the top 5/10 tables and indexes to their own space made a greater impact. Someone who reads PostgreSQL 8.0 Performance Checklist is going to see point #1 add more disks is the key. How about adding a subpoint to explaining when more disks isn't enough or applicable? I maybe generalizing the complexity of tuning an OLTP application, but some clarity could help. Steve Poe