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 C9946329DBE for ; Sat, 9 Oct 2004 16:05:28 +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 79030-09 for ; Sat, 9 Oct 2004 15:05:18 +0000 (GMT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 0433832A928 for ; Sat, 9 Oct 2004 16:05:16 +0100 (BST) Received: from ool-43529386.dyn.optonline.net ([67.82.147.134] helo=[192.168.1.9]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42) id 1CGImZ-0000Rs-DG; Sat, 09 Oct 2004 11:05:15 -0400 Message-ID: <4167FD71.9050501@zeut.net> Date: Sat, 09 Oct 2004 11:02:09 -0400 From: Matthew User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some References: <200410081443.16109.josh@agliodbs.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 67.82.147.134 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: Zeut 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: 200410/120 X-Sequence-Number: 8596 Christopher Browne wrote: >josh@agliodbs.com (Josh Berkus) wrote: > > >>This result is so surprising that I want people to take a look at it >>and tell me if there's something wrong with the tests or some >>bottlenecking factor that I've not seen. >> >> >I'm aware of two conspicuous scenarios where ARC would be expected to >_substantially_ improve performance: > > 1. When it allows a VACUUM not to throw useful data out of > the shared cache in that VACUUM now only 'chews' on one > page of the cache; > Right, Josh, I assume you didn't run these test with pg_autovacuum running, which might be interesting. Also how do these numbers compare to 7.4? They may not be what you expected, but they might still be an improvment. Matthew