X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4FFDD474E5C for ; Fri, 21 Feb 2003 04:14:50 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 64493-01 for ; Fri, 21 Feb 2003 04:14:39 -0500 (EST) Received: from grunt26.ihug.com.au (grunt26.ihug.com.au [203.109.249.146]) by postgresql.org (Postfix) with ESMTP id 5AEC8474E4F for ; Fri, 21 Feb 2003 04:14:39 -0500 (EST) Received: from p148-tnt1.adl.ihug.com.au (postgresql.org) [203.173.248.148] by grunt26.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 18m9GP-0007hx-00; Fri, 21 Feb 2003 20:14:38 +1100 Message-ID: <3E55EE62.6010909@postgresql.org> Date: Fri, 21 Feb 2003 19:46:18 +1030 From: Justin Clift User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakab Laszlo Cc: Christopher Kings-Lynne , pgsql-performance@postgresql.org Subject: Re: performance issues for processing more then 150000 References: <004501c2d97d$98927670$0900000a@new> <0a6901c2d97f$ea1369d0$6500a8c0@fhp.internal> <007c01c2d983$f3d60d70$0900000a@new> In-Reply-To: <007c01c2d983$f3d60d70$0900000a@new> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/147 X-Sequence-Number: 1203 Jakab Laszlo wrote: > Hello Chris, > > I mean here 150000 inserts/day ( quickly grows constantly )... - with > transactions and on the same table ... maybe after one significant > amount of time we can move the records of one year to one archive table ... > And some 2-3 millions of selects / day ... That's no problem at all, depending on: + How complex are the queries you're intending on running? + How will the data be spread between the tables? + The amount of data per row also makes a difference, if it is extremely large. > I would like to know also some hardware related advice. You're almost definitely going to be needing a SCSI or better RAID array, plus a server with quite a few GB's of ECC memory. If you need to get specific about hardware to the point of knowing exactly what you're needing, you're likely best to pay a good PostgreSQL consultant to study your proposal in depth. Hope this helps. Regards and best wishes, Justin Clift > thanks, > Jaki -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi