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 7C210D1B21B for ; Mon, 2 Aug 2004 19:18:30 -0300 (ADT) 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 47969-08 for ; Mon, 2 Aug 2004 22:18:15 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id EFD96D1B16E for ; Mon, 2 Aug 2004 19:18:12 -0300 (ADT) 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 i72MICqb070761 for ; Mon, 2 Aug 2004 22:18:12 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i72MEM1w070288 for pgsql-performance@postgresql.org; Mon, 2 Aug 2004 22:14:22 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Page Miss Hits Date: Tue, 03 Aug 2004 00:13:56 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 54 Message-ID: <410EBCA4.9000508@bigfoot.com> References: <1091463567.27166.44.camel@localhost.localdomain> <410E6F34.6040300@bigfoot.com> <1091468476.27166.48.camel@localhost.localdomain> <410EA90C.7030707@bigfoot.com> <1091481975.36221.138.camel@jester> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Rod Taylor User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en In-Reply-To: <1091481975.36221.138.camel@jester> X-Enigmail-Version: 0.84.2.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: 200408/23 X-Sequence-Number: 7659 Rod Taylor wrote: >>| ARC still helps, since it makes sure the shared_buffers don't all get >>| flushed from the useful small datasets when a seq scan gets executed. >> >>I'm still not convinced. Why the last backend alive, have to throw away >>bunch of memory copied in the SHM? And again, the ARC is a replacement >>policy for a cache, which one ? > > > As you know, ARC is a recent addition. I've not seen any benchmarks > demonstrating that the optimal SHARED_BUFFERS setting is different today > than it was in the past. > > We know it's changed, but the old buffer strategy had an equally hard > time with a small buffer as it did a large one. Does that mean the > middle of the curve is still at 15k buffers but the extremes are handled > better? Or something completely different? > > Please feel free to benchmark 7.5 (OSDL folks should be able to help us > as well) and report back. I know, I know. We were discussing about the fact that postgres use a his own cache or not; and for the OP pleasure then if is possible retrieve hit and miss information from that cache. For benchmarch may be is better that you look not at the particular implementation done in postgresql but at the general improvements that the ARC replacement policy introduce. If I'm not wrong till now postgres was using an LRU, around you can find some articles like these: http://www.almaden.ibm.com/StorageSystems/autonomic_storage/ARC/rj10284.pdf http://www.almaden.ibm.com/cs/people/dmodha/arcfast.pdf where are showns the improvements. As you wrote no one did benchmarks on demostrating with the "brute force" that ARC is better but on the paper should be. Regards Gaetano Mendola