X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 26F6CD6E94 for ; Mon, 21 Nov 2005 05:58:50 -0400 (AST) 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 94450-01 for ; Mon, 21 Nov 2005 09:58:51 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.eulerhermes.pl (host-ip43-68.crowley.pl [85.128.68.43]) by svr1.postgresql.org (Postfix) with ESMTP id 7B9EBD9632 for ; Mon, 21 Nov 2005 05:58:46 -0400 (AST) Received: from [192.168.49.9] (helo=xterm.podsiec) by mail.eulerhermes.pl with esmtpa (Exim 4.42) id 1Ee8Rh-0001v1-GX; Mon, 21 Nov 2005 10:58:45 +0100 From: Marcin Giedz Organization: Euler Hermes To: pgsql-admin@postgresql.org, mario.splivalo@mobart.hr Subject: Re: Server Hardware Configuration Date: Mon, 21 Nov 2005 10:58:41 +0100 User-Agent: KMail/1.7.1 References: <20051120175337.GP19279@pervasive.com> <1132565676.8689.9.camel@ekim> In-Reply-To: <1132565676.8689.9.camel@ekim> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511211058.41632.marcin.giedz@eulerhermes.pl> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/274 X-Sequence-Number: 19647 Dnia poniedzia=B3ek, 21 listopada 2005 10:34, Mario Splivalo napisa=B3: > On Sun, 2005-11-20 at 11:53 -0600, Jim C. Nasby wrote: > > Two general comments: most people find that Opterons perform much better > > than Xeons. With some versions of PostgreSQL, the difference is over > > 50%. > > Could you be more specific on that? Which version of Postgres perform > better on Opteron than on Xeon? Try http://85.128.68.44 - I made some test about Xeon and Opteron=20 > > > RAID5 generally doesn't make for a fast database. The problem is that > > there is a huge amount of overhead everytime you go to write something > > out to a RAID5 array. With careful tuning of the background writer you > > might be able to avoid some of that penalty, though your read > > performance will likely still be affected by the write overhead. > > RAID5 was not ment to improve performance, but to minimize disaster and > downtime when your hard disk dies. We're using RAID5 with postgres. In > the last 3 years we changed 5 disks, but the system downtime was zero > minutes. I'm ready enough to put some tests about different RAID's for Postgresql - = but=20 I will soon. However almost all people I know preffer RAID10 for database=20 like PGSQL. Marcin > > > Mike