Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 98805B5DC08 for ; Thu, 4 Aug 2011 02:07:13 -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 06141-03 for ; Thu, 4 Aug 2011 05:07:07 +0000 (UTC) X-Greylist: delayed 01:03:36.239007 by SQLgrey-1.7.6 Received: from mail-pz0-f42.google.com (mail-pz0-f42.google.com [209.85.210.42]) by mail.postgresql.org (Postfix) with ESMTP id 71A6EB5D800 for ; Thu, 4 Aug 2011 02:07:05 -0300 (ADT) Received: by pzk37 with SMTP id 37so2045580pzk.15 for ; Wed, 03 Aug 2011 22:07:05 -0700 (PDT) Received: by 10.143.41.18 with SMTP id t18mr317220wfj.124.1312430609254; Wed, 03 Aug 2011 21:03:29 -0700 (PDT) Received: from [10.0.0.53] (office1.postnewspapers.com.au [150.101.171.128]) by mx.google.com with ESMTPS id n2sm599741wfd.11.2011.08.03.21.03.26 (version=SSLv3 cipher=OTHER); Wed, 03 Aug 2011 21:03:28 -0700 (PDT) Message-ID: <4E3A1A0B.5090809@ringerc.id.au> Date: Thu, 04 Aug 2011 12:03:23 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Parameters for PostgreSQL References: <4E373D76.9020800@postnewspapers.com.au> In-Reply-To: Content-Type: multipart/alternative; boundary="------------070102080701010205010008" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201108/43 X-Sequence-Number: 44490 This is a multi-part message in MIME format. --------------070102080701010205010008 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 04/08/11 11:42, Jayadevan M wrote: > Hello, > > >The most important spec has been omitted. What's the storage subsystem? > We have storage on SAN, RAID 5. RAID 5? That's *really* not ideal for database workloads, either Pg or Oracle, unless your RAID 5 storage backend has enough battery-backed write cache to keep huge amounts of writes in RAM and reorder them really effectively. I hope each RAID 5 LUN is only across a few disks and is layered with RAID 1, though. RAID 5 becomes less reliable than using a single disk when used with too many HDDs, because the probability of a double-disk failure becomes greater than that of a single standalone disk failing. After being bitten by that a few times, these days I'm using RAID 6 in most cases where RAID 10 isn't practical. In any case, "SAN" can be anything from a Linux box running an iSCSI target on top of a RAID 5 `md' software RAID volume on four 5400RPM HDDs, right up to a giant hundreds-of-fast-disks monster filer full of dedicated ASICs and great gobs of battery backed write cache DRAM. Are you able to be any more specific about what you're dealing with? > > > > We are suing weblogic. > > ^^^^^ > > Best. Typo. Ever. > > > > I hear most people who use it want to, you're just brave enough to > do it :-P > I wish I could make a few millions that way. > > > Thank you for all the replies. The first step is, of course, to > migrate the data. I am working with ora2pg for that. I assume creating > files with 'COPY' to work as input for PostgreSQL is the right > approach? We don't have many stored procedures or packages. So that > part should be OK. --------------070102080701010205010008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 04/08/11 11:42, Jayadevan M wrote:
Hello,

>The most important spec has been omitted. What's the storage subsystem?

We have storage on SAN, RAID 5.

RAID 5? That's *really* not ideal for database workloads, either Pg or Oracle, unless your RAID 5 storage backend has enough battery-backed write cache to keep huge amounts of writes in RAM and reorder them really effectively.

I hope each RAID 5 LUN is only across a few disks and is layered with RAID 1, though. RAID 5 becomes less reliable than using a single disk when used with too many HDDs, because the probability of a double-disk failure becomes greater than that of a single standalone disk failing. After being bitten by that a few times, these days I'm using RAID 6 in most cases where RAID 10 isn't practical.

In any case, "SAN" can be anything from a Linux box running an iSCSI target on top of a RAID 5 `md' software RAID volume on four 5400RPM HDDs, right up to a giant hundreds-of-fast-disks monster filer full of dedicated ASICs and great gobs of battery backed write cache DRAM. Are you able to be any more specific about what you're dealing with?

 
> > We are suing weblogic.
>           ^^^^^
> Best. Typo. Ever.
>
> I hear most people who use it want to, you're just brave enough to do it :-P
I wish I could make a few millions that way.



Thank you for all the replies. The first step is, of course, to migrate the data. I am working with ora2pg for that. I assume creating files with 'COPY' to work as input for PostgreSQL is the right approach? We don't have many stored procedures or packages. So that part should be OK.


--------------070102080701010205010008--