Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E11C4B5DBC0 for ; Thu, 16 Jun 2011 15:29:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 39447-07 for ; Thu, 16 Jun 2011 18:29:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from shrek.krogh.cc (2605ds1-ynoe.0.fullrate.dk [90.184.12.24]) by mail.postgresql.org (Postfix) with ESMTP id 94753B5DBBF for ; Thu, 16 Jun 2011 15:29:34 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 388153390AE; Thu, 16 Jun 2011 20:29:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Ur3iu3ox0-d; Thu, 16 Jun 2011 20:29:30 +0200 (CEST) Received: from [90.184.13.151] (2605ds1-ynoe.2.fullrate.dk [90.184.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id 236EC339091; Thu, 16 Jun 2011 20:29:30 +0200 (CEST) Message-ID: <4DFA4B89.6080504@krogh.cc> Date: Thu, 16 Jun 2011 20:29:29 +0200 From: Jesper Krogh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: Haestan CC: pgsql-performance@postgresql.org Subject: Re: Performance advice for a new low(er)-power server References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201106/142 X-Sequence-Number: 44075 On 2011-06-16 17:09, Haestan wrote: > I am evaluating hardware for a new PostgreSQL server. For reasons > concerning power consumption and available space it should not have > more than 4 disks (in a 1U case), if possible. Now, I am not sure what > disks to use and how to layout them to get the best performance. What is your data:memory-size ratio? Can you afford to have everything in memory and only have the disks to be able to sustain writes? > The cheaper option would be to buy 15k Seagate SAS disks with a 3ware > 9750SA (battery backed) controller. Does it matter whether to use a > 4-disk RAID10 or 2x 2-disk RAID1 (system+pg_xlog , pg_data) setup? Am > I right that both would be faster than just using a single 2-disk > RAID1 for everything? > > A higher end option would be to use 2x 64G Intel X-25E SSD's with a > LSI MegaRAID 9261 controller for pg_data and/or pg_xlog and 2x SAS > disks for the rest. Unfortunately, these SSD are the only ones offered > by our supplier and they don't use a supercapacitor, AFAIK. Therefore > I would have to disable the write cache on the SSD's somehow and just > use the cache on the controller only. Does anyone know if this will > work or even uses such a setup. Any SSD is orders of magnitude better than any rotating drive in terms of random reads. If you will benefit depends on your data:memory ratio.. > Furthermore, the LSI MegaRAID 9261 offers CacheCade which uses SSD > disks a as secondary tier of cache for the SAS disks. Would this > feature make sense for a PostgreSQL server, performance wise? I have one CacheCade setup... not a huge benefit but it seems measurable. (but really hard to test). .. compared to a full SSD-setup I wouldn't consider it at all. -- Jesper