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 67588329CBC for ; Sat, 18 Sep 2004 01:07:44 +0100 (BST) 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 59838-03 for ; Sat, 18 Sep 2004 00:07:37 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 17911329C67 for ; Sat, 18 Sep 2004 01:07:36 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i8I07WCn061859 for ; Sat, 18 Sep 2004 00:07:32 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i8HNgX1i056228 for pgsql-performance@postgresql.org; Fri, 17 Sep 2004 23:42:33 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Tryint to match Solaris-Oracle performance with directio? Date: Sat, 18 Sep 2004 01:42:25 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 28 Message-ID: <414B7661.7000108@bigfoot.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: ischamay.andbergsay@activestateway.com User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/188 X-Sequence-Number: 8316 Mischa Sandberg wrote: > In the meantime, what I gather from browsing mail archives is that > postgresql on Solaris seems to get hung up on IO rather than CPU. > Furthermore, I notice that Oracle and now MySQL use directio to bypass > the system cache, when doing heavy writes to the disk; and Postgresql > does not. > > Not wishing to alter backend/store/file for this test, I figured I could > get a customer to mount the UFS volume for pg_xlog with the option > "forcedirectio". > > Any comment on this? No consideration of what the wal_sync_method is at > this point. Presumably it's defaulting to fdatasync on Solaris. > > BTW this is Postgres 7.4.1, and our customers are Solaris 8 and 9. If you care your data upgrade to more recent 7.4.5 Test your better sync method using /src/tools/fsync however do some experiment changing the sync method, you can also avoid to update the acces time for the inodes mounting the partition with noatime option ( this however have more impact on performance for read activities ) Regards Gaetano Mendola