Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 61A33632894 for ; Thu, 3 Jun 2010 13:52:57 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 61122-05 for ; Thu, 3 Jun 2010 16:52:50 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 18468632726 for ; Thu, 3 Jun 2010 13:52:49 -0300 (ADT) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MaX6b-1OdfFf10kj-00K1bZ; Thu, 03 Jun 2010 18:52:46 +0200 Message-ID: <4C07DDDC.6000003@2ndquadrant.com> Date: Thu, 03 Jun 2010 12:52:44 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Craig James CC: pgsql-performance@postgresql.org Subject: Re: Weird XFS WAL problem References: <4C06E994.2080905@emolecules.com> In-Reply-To: <4C06E994.2080905@emolecules.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/KtJaFTXOiNElg/EVt0gJUqt+CUuhglYun9YB jF1DOeZ+KX+tiFefGMyx+Xpi/gn7z+8r586NDdS+H3F4dzL7er ROidoo6hmhQ1l3GkI7Q55k0bDvRl4Ri X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/55 X-Sequence-Number: 38911 Craig James wrote: > I'm testing/tuning a new midsize server and ran into an inexplicable > problem. With an RAID10 drive, when I move the WAL to a separate > RAID1 drive, TPS drops from over 1200 to less than 90! Normally <100 TPS means that the write cache on the WAL drive volume is disabled (or set to write-through instead of write-back). When things in this area get fishy, I will usually download sysbench and have it specifically test how many fsync calls can happen per second. http://projects.2ndquadrant.com/talks , "Database Hardware Benchmarking", page 28 has an example of the right incantation for that. Also, make sure you run 3ware's utilities and confirm all the disks have finished their initialization and verification stages. If you just adjusted disk layout that and immediate launched into benchmarks, those are useless until the background cleanup is done. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us