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 46E0C3A3B09 for ; Fri, 5 Nov 2004 04:34:00 +0000 (GMT) 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 45100-02 for ; Fri, 5 Nov 2004 04:33:58 +0000 (GMT) Received: from sue.samurai.com (sue.samurai.com [205.207.28.74]) by svr1.postgresql.org (Postfix) with ESMTP id EB9D43A1D85 for ; Fri, 5 Nov 2004 04:33:57 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by sue.samurai.com (Postfix) with ESMTP id 0E9BA19811; Thu, 4 Nov 2004 23:33:57 -0500 (EST) Received: from sue.samurai.com ([127.0.0.1]) by localhost (sue.samurai.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 65205-01-8; Thu, 4 Nov 2004 23:33:53 -0500 (EST) Received: from [61.88.101.19] (unknown [61.88.101.19]) by sue.samurai.com (Postfix) with ESMTP id CA09D19801; Thu, 4 Nov 2004 23:33:52 -0500 (EST) Subject: Re: Anything to be gained from a 'Postgres Filesystem'? From: Neil Conway To: =?ISO-8859-1?Q?Pierre-Fr=E9d=E9ric?= Caillaud Cc: pgsql-performance@postgresql.org In-Reply-To: References: <20041104120047.62810c8f@kingfisher.intern.logi-track.com> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1099629212.10449.45.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 05 Nov 2004 15:33:32 +1100 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mailbox.samurai.com 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: 200411/83 X-Sequence-Number: 9037 On Thu, 2004-11-04 at 23:29, Pierre-Frédéric Caillaud wrote: > There is also the fact that syncing after every transaction could be > changed to syncing every N transactions (N fixed or depending on the data > size written by the transactions) which would be more efficient than the > current behaviour with a sleep. Uh, which "sleep" are you referring to? Also, how would interacting with the filesystem's journal effect how often we need to force-write the WAL to disk? (ISTM we need to sync _something_ to disk when a transaction commits in order to maintain the WAL invariant.) > There's fadvise to tell the OS to readahead on a seq scan (I think the OS > detects it anyway) Not perfectly, though; also, Linux will do a more aggressive readahead if you tell it to do so via posix_fadvise(). > if there was a system call telling the OS "in the > next seconds I'm going to read these chunks of data from this file (gives > a list of offsets and lengths), could you put them in your cache in the > most efficient order without seeking too much, so that when I read() them > in random order, they will be in the cache already ?". http://www.opengroup.org/onlinepubs/009695399/functions/posix_fadvise.html POSIX_FADV_WILLNEED Specifies that the application expects to access the specified data in the near future. -Neil