Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 43AD99FBC79 for ; Wed, 30 May 2007 17:14:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 33934-03 for ; Wed, 30 May 2007 17:14:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from chip2og56.obsmtp.com (chip2og56.obsmtp.com [64.18.13.49]) by postgresql.org (Postfix) with SMTP id 2E1C09FB7B3 for ; Wed, 30 May 2007 17:14:18 -0300 (ADT) Received: from source ([63.240.6.44]) (using TLSv1) by chip2ob56.postini.com ([64.18.5.12]) with SMTP; Wed, 30 May 2007 13:14:06 PDT Received: from 172.16.1.92 by mail.mi8.com with ESMTP (- Welcome to Mi8 Corporation www.Mi8.com (D4)); Wed, 30 May 2007 16:14:01 -0400 X-Server-Uuid: C8FB4D43-1108-484A-A898-3CBCC7906230 Received: from MI8NYCMAIL08.Mi8.com ([172.16.1.165]) by d01smtp08.Mi8.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 May 2007 16:14:00 -0400 Received: from 63.80.24.130 ([63.80.24.130]) by MI8NYCMAIL08.Mi8.com ( [172.16.1.190]) via Exchange Front-End Server mi8owa.mi8.com ( [172.16.1.134]) with Microsoft Exchange Server HTTP-DAV ; Wed, 30 May 2007 20:13:47 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Wed, 30 May 2007 13:13:45 -0700 Subject: Re: Bad RAID1 read performance From: "Luke Lonergan" To: "Albert Cervera Areny" , pgsql-performance@postgresql.org Message-ID: Thread-Topic: [PERFORM] Bad RAID1 read performance Thread-Index: Acei9wZRRRiMMg7qEdy5oAAX8s8Cag== In-Reply-To: <200705301700.26704.albert@sedifa.com> MIME-Version: 1.0 X-OriginalArrivalTime: 30 May 2007 20:14:00.0888 (UTC) FILETIME=[0FCA3380:01C7A2F7] X-WSS-ID: 6A43048C1AG15598063-09-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/627 X-Sequence-Number: 25017 Albert, On 5/30/07 8:00 AM, "Albert Cervera Areny" wrote: > Hardware isn't very good I believe, and it's about 2-3 years old, but the RAID > is Linux software, and though not very good the difference between reading > and writing should probably be greater... (?) Not for one thread/process of I/O. Mirror sets can nearly double the read performance on most RAID adapters or SW RAID when using two or more thread/processes, but a single thread will get one drive worth of performance. You should try running two simultaneous processes during reading and see what you get. > Would you set 512Kb readahead on both drives and RAID? I tried various > configurations and none seemed to make a big difference. It seemed correct to > me to set 512kb per drive and 1024kb for md0. Shouldn't matter that much, but yes, each drive getting half the readahead is a good strategy. Try 256+256 and 512. The problem you have is likely not related to the readahead though - I suggest you try read/write to a single disk and see what you get. You should get around 60 MB/s if the drive is a modern 7200 RPM SATA disk. If you aren't getting that on a single drive, there's something wrong with the SATA driver or the drive(s). - Luke > A Dimecres 30 Maig 2007 16:09, Luke Lonergan va escriure: >> This sounds like a bad RAID controller - are you using a built-in hardware >> RAID? If so, you will likely want to use Linux software RAID instead. >> >> Also - you might want to try a 512KB readahead - I've found that is optimal >> for RAID1 on some RAID controllers. >> >> - Luke >> >> On 5/30/07 2:35 AM, "Albert Cervera Areny" wrote: >>> Hi, >>> after doing the "dd" tests for a server we have at work I obtained: >>> Read: 47.20 Mb/s >>> Write: 39.82 Mb/s >>> Some days ago read performance was around 20Mb/s due to no readahead in >>> md0 so I modified it using hdparm. However, it seems to me that being it >>> a RAID1 read speed could be much better. These are SATA disks with 3Gb of >>> RAM so I did 'time bash -c "dd if=/dev/zero of=bigfile bs=8k count=786432 >>> && sync"'. File system is ext3 (if read many times in the list that XFS >>> is faster), but I don't want to change the file system right now. >>> Modifing the readahead from the current 1024k to 2048k doesn't make any >>> difference. Are there any other tweaks I can make? >>> >>> >>> ---------------------------(end of broadcast)--------------------------- >>> TIP 4: Have you searched our list archives? >>> >>> http://archives.postgresql.org >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 6: explain analyze is your friend