X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7908053657 for ; Thu, 24 Mar 2005 09:35:05 +0000 (GMT) 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 42542-07 for ; Thu, 24 Mar 2005 09:35:02 +0000 (GMT) Received: from felix.adpcl.com (felix.adpcl.com [194.98.137.100]) by svr1.postgresql.org (Postfix) with ESMTP id 5345C533FD for ; Thu, 24 Mar 2005 09:34:59 +0000 (GMT) Received: from pcpatrickxp (unknown [150.175.11.30]) by felix.adpcl.com (Postfix) with SMTP id 127247804; Thu, 24 Mar 2005 10:38:04 +0100 (NFT) Message-ID: <004d01c53054$965583e0$1e0baf96@pcpatrickxp> From: "Patrick Vedrines" To: "Gustavo F Nobrega - Planae" Cc: "performance pgsql" References: <002601c52f0a$2312a4d0$280baf96@PCPATRICK> <424063BC.3050206@planae.com.br> Subject: Re: CPU 0.1% IOWAIT 99% for decisonnal queries Date: Thu, 24 Mar 2005 10:33:50 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004A_01C5305C.F7FD3C20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.474 tagged_above=0 required=5 tests=AWL, HTML_50_60, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200503/498 X-Sequence-Number: 11203 This is a multi-part message in MIME format. ------=_NextPart_000_004A_01C5305C.F7FD3C20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Gustavo, Your question seems to say that you suspect a disk issue, and a few = hours later, Simon told me "Sounds like your disks/layout/something is = pretty sick". To be clear in my own mind about it, I've just copyed (time cp) the = "aggregate" table files (4 Gb) from one disk to an another one: it takes = 22 mn !(3 Mb/s). That seems to demonstrate that Postgres is not the cause of this issue.=20 I've just untrusted to my system engineer the analysis of my disks... In case I would have to change my disks, do you have any performance = figures related to the types you mentionned (reiserfs vs ext3) ? I don't use RAID since the security is not a concern. Thank a lot for your help ! Patrick Hi Patrick, How is configured your disk array? Do you have a Perc 4? Tip: Use reiserfs instead ext3, raid 0+1 and deadline I/O scheduler in = kernel linux 2.6 ------=_NextPart_000_004A_01C5305C.F7FD3C20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello Gustavo,
 
Your question seems to say that you = suspect a disk=20 issue, and a few hours later, Simon told me "Sounds like your=20 disks/layout/something is pretty sick".
To be clear in my own mind about it, = I've just=20 copyed (time cp) the "aggregate" table files (4 Gb) from one disk to an = another=20 one: it takes 22 mn !(3 Mb/s).
That seems to demonstrate that Postgres = is not the=20 cause of this issue.
I've just untrusted to my system = engineer the=20 analysis of my disks...
 
In case I would have to change my = disks, do you=20 have any performance figures related to the types you mentionned = (reiserfs=20 vs ext3) ?
I don't use RAID since the security is = not a=20 concern.
 
Thank a lot for your help = !
 
Patrick
 
Hi=20 Patrick,

    How is configured your disk array? = Do you=20 have a Perc 4?

Tip: Use reiserfs instead ext3, raid 0+1 and = deadline=20 I/O scheduler in kernel linux 2.6
 
------=_NextPart_000_004A_01C5305C.F7FD3C20--