X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1C776D1B4ED; Thu, 25 Mar 2004 21:47:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 90557-09; Thu, 25 Mar 2004 17:47:29 -0400 (AST) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id C65C6D1EC85; Thu, 25 Mar 2004 17:47:22 -0400 (AST) Received: from osdl.org (markw@ibm-b.pdx.osdl.net [172.20.1.51]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id i2PLkx209812; Thu, 25 Mar 2004 13:47:00 -0800 Message-Id: <200403252147.i2PLkx209812@mail.osdl.org> Date: Thu, 25 Mar 2004 13:46:56 -0800 (PST) From: markw@osdl.org Subject: Re: [HACKERS] fsync method checking To: tgl@sss.pgh.pa.us Cc: josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <6391.1079977274@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/366 X-Sequence-Number: 6222 On 22 Mar, Tom Lane wrote: > markw@osdl.org writes: >> I could certainly do some testing if you want to see how DBT-2 does. >> Just tell me what to do. ;) > > Just do some runs that are identical except for the wal_sync_method > setting. Note that this should not have any impact on SELECT > performance, only insert/update/delete performance. Ok, here are the results I have from my 4-way xeon system, a 14 disk volume for the log and a 52 disk volume for everything else: http://developer.osdl.org/markw/pgsql/wal_sync_method.html 7.5devel-200403222 wal_sync_method metric default (fdatasync) 1935.28 fsync 1613.92 # ./test_fsync -f /opt/pgdb/dbt2/pg_xlog/test.out Simple write timing: write 0.018787 Compare fsync times on write() and non-write() descriptor: (If the times are similar, fsync() can sync data written on a different descriptor.) write, fsync, close 13.057781 write, close, fsync 13.311313 Compare one o_sync write to two: one 16k o_sync write 6.515122 two 8k o_sync writes 12.455124 Compare file sync methods with one 8k write: (o_dsync unavailable) open o_sync, write 6.270724 write, fdatasync 13.275225 write, fsync, 13.359847 Compare file sync methods with 2 8k writes: (o_dsync unavailable) open o_sync, write 12.479563 write, fdatasync 13.651709 write, fsync, 14.000240