Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 777A12E0030 for ; Fri, 20 Jun 2008 08:07:09 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 99422-08 for ; Fri, 20 Jun 2008 08:07:01 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by developer.postgresql.org (Postfix) with ESMTP id 3CA902E0038 for ; Fri, 20 Jun 2008 08:07:06 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id m5KB71L1003612 for ; Fri, 20 Jun 2008 08:07:01 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id m5KArkUn088489 for pgsql-performance@postgresql.org; Fri, 20 Jun 2008 07:53:46 -0300 (ADT) (envelope-from news) From: "Lionel" X-Newsgroups: pgsql.performance Subject: Re: Which hardware ? Date: Fri, 20 Jun 2008 12:53:45 +0200 Organization: Hub.Org Networking Services Lines: 29 Message-ID: References: <20080617142501.GG68434@commandprompt.com> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-RFC2646: Format=Flowed; Original To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/101 X-Sequence-Number: 30451 "Scott Marlowe" wrote: > We had a reporting server with about 80G of data on a machine with 4G > ram last place I worked, and it could take it a few extra seconds to > hit the old data, but the SW RAID-10 on it made it much faster at > reporting than it would have been with a single disk. Would this be a nice choice ? HP Proliant DL320 G5p Xeon DC 3 GHz - 8 Go RAM DDR2 ECC - 4 x 146 Go SAS 15k rpm - RAID-10 HP Smart Array (128 Mo cache) I finally choose to have 2 data tables: - one with pre aggregated (dividing size by 10), unpartitionned (=the database they currently use) - one with original data, yearly partitionned I will choose before each statement which table will be used depending on which select/joins/where/groupby the user choosed. The aggregated datas will allow me to maintain actual performances (and even improve it using the new hardware twice more powerfull). I think lines aggregation will be handled by the java application (excel/csv file loaded in memory), which will be much faster than using a trigger on insertion in the full table. Thanks.