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 059A5536A4 for ; Sat, 26 Mar 2005 00:24:14 +0000 (GMT) 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 17059-01 for ; Sat, 26 Mar 2005 00:24:13 +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 1E34053691 for ; Sat, 26 Mar 2005 00:24:12 +0000 (GMT) Received: from mail pickup service by mail.tecarta.com with Microsoft SMTPSVC; Fri, 25 Mar 2005 16:27:10 -0800 Received: from mail.tecarta.com ([192.168.160.2]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 25 Mar 2005 16:27:09 -0800 Received: from barracuda.tecarta.com ([192.168.160.200]) by mail.tecarta.com (SAVSMTP 3.1.0.29) with SMTP id M2005032516270814647 for ; Fri, 25 Mar 2005 16:27:08 -0800 X-ASG-Debug-ID: 1111796654-2762-3-0 X-Barracuda-URL: http://192.168.160.200:8000/cgi-bin/mark.cgi Received: from mail2 (mail2.hq.corp [192.168.160.6]) by barracuda.tecarta.com (Spam Firewall) with SMTP id 281F42003DC6 for ; Fri, 25 Mar 2005 16:24:14 -0800 (PST) Received: from [192.168.0.13] ([63.206.203.145]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 25 Mar 2005 16:27:04 -0800 Message-ID: <42443863.4040302@sfnet.cc> Date: Fri, 25 Mar 2005 16:12:19 +0000 From: Steve Poe User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Accept-Language: en-us, en MIME-Version: 1.0 To: performance pgsql X-ASG-Orig-Subj: How to improve db performance with $7K? Subject: How to improve db performance with $7K? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Mar 2005 00:27:04.0504 (UTC) FILETIME=[891D2380:01C5319A] X-Virus-Scanned: by Barracuda Spam Firewall at tecarta.com X-Barracuda-Spam-Score: 0.85 X-Barracuda-Spam-Status: No, SCORE=0.85 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=DATE_IN_PAST_06_12 X-Barracuda-Spam-Report: Code version 2.64, rules version 2.1.2137 Rule breakdown below pts rule name description ---- ---------------------- ------------------------------------------- 0.85 DATE_IN_PAST_06_12 Date: is 6 to 12 hours before Received: date X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.267 tagged_above=0 required=5 tests=AWL, DATE_IN_PAST_06_12, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/575 X-Sequence-Number: 11280 Situation: An 24/7 animal hospital (100 employees) runs their business on Centos 3.3 (RHEL 3) Postgres 7.4.2 (because they have to) off a 2-CPU Xeon 2.8MHz, 4GB of RAM, (3) SCSI disks RAID 0 (zcav value 35MB per sec). The databse is 11GB comprised over 100 tables and indexes from 1MB to 2GB in size. I recently told the hospital management team worst-case scenerio they need to get the database on its own drive array since the RAID0 is a disaster wating to happen. I said ideally a new dual AMD server with 6/7-disk configuration would be ideal for safety and performance, but they don't have $15K. I said a seperate drive array offer the balance of safety and performance. I have been given budget of $7K to accomplish a safer/faster database through hardware upgrades. The objective is to get a drive array, but I can use the budget any way I see fit to accomplish the goal. Since I am a dba novice, I did not physically build this server, nor did I write the application the hospital runs on, but I have the opportunity to make it better, I'd thought I should seek some advice from those who have been down this road before. Suggestions/ideas anyone? Thanks. Steve Poe