Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 19DC31337B7D for ; Wed, 17 Nov 2010 18:48:45 -0400 (AST) 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 32554-07-2 for ; Wed, 17 Nov 2010 22:48:39 +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 95C561337B97 for ; Wed, 17 Nov 2010 18:48:37 -0400 (AST) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Lm6OP-1Ok41335ph-00ZeUK; Wed, 17 Nov 2010 23:48:33 +0100 Message-ID: <4CE45BBF.7000507@2ndquadrant.com> Date: Wed, 17 Nov 2010 17:48:31 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Jon Nelson CC: Scott Carey , Marti Raudsepp , "pgsql-performance@postgresql.org" Subject: Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1? References: <4CCDCAA3.4050805@2ndquadrant.com> <201011010010.28724.andres@anarazel.de> <4CD472CC.80006@2ndquadrant.com> <4CE2EBF8.4040602@2ndquadrant.com> <499BFB3F-CD9F-47D2-87E4-058C2A6D63EC@richrelevance.com> <4CE44826.2070508@2ndquadrant.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:6LNCnxJ2lv/75bXGafSeu9YoLTW2zEzFTaKvgJviqA6 1nLCwYE1V/0F8zFHaKnb7zv8A41I/sS4vDNoESnLhx5nR9jcGP qKRGojE/6wPlI88HcvF7V7rhabMWnERXAnm5vrd4nnrJmGix0+ ynY89MPDmL2xC7fRl1wf51P0kY9qsh2fXGXOfTc63f9kGtTOER cJVfr3mK6iwlj7NYqVnMfyD6As/NimUQqZw+fIivbM= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201011/301 X-Sequence-Number: 41325 Jon Nelson wrote: > One thing to note is that where on a disk things sit can make a /huge/ > difference - depending on if Ubuntu is /here/ and RHEL is /there/ and > so on can make a factor of 2 or more difference. The outside tracks > of most modern SATA disks can do around 120MB/s. The inside tracks > aren't even half of that. > You're talking about changes in sequential read and write speed due to Zone Bit Recording (ZBR) AKA Zone Constant Angular Velocity (ZCAV). What I was measuring was commit latency time on small writes. That doesn't change as you move around the disk, since it's tied to the raw rotation speed of the drive rather than density of storage in any zone. If I get to something that's impacted by sequential transfers rather than rotation time, I'll be sure to use the same section of disk for that. It wasn't really necessary to get these initial gross numbers anyway. What I was looking for is the about 10:1 speedup seen on this hardware when the write cache is used, which could easily be seen even were there ZBR differences involved. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books