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 21E0632A10B for ; Fri, 8 Oct 2004 23:40:02 +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 85227-06 for ; Fri, 8 Oct 2004 22:39:49 +0000 (GMT) Received: from trofast.sesse.net (trofast.sesse.net [129.241.93.32]) by svr1.postgresql.org (Postfix) with ESMTP id 04769329E5C for ; Fri, 8 Oct 2004 23:39:51 +0100 (BST) Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1CG3Or-0003vH-00 for ; Sat, 09 Oct 2004 00:39:45 +0200 Date: Sat, 9 Oct 2004 00:39:45 +0200 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, Message-ID: <20041008223945.GA15067@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: <200410081443.16109.josh@agliodbs.com> <1097273580.25588.18.camel@vulture.corp.neopolitan.com> <21489.1097274752@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21489.1097274752@sss.pgh.pa.us> X-Operating-System: Linux 2.6.6 on a i686 User-Agent: Mutt/1.5.6+20040818i 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/115 X-Sequence-Number: 8591 On Fri, Oct 08, 2004 at 06:32:32PM -0400, Tom Lane wrote: > This does raise a question for Josh though, which is "where's the > oprofile results?" If we do have major problems at the level of cache > misses then oprofile would be able to prove it. Or cachegrind. I've found it to be really effective at pinpointing cache misses in the past (one CPU-intensive routine was sped up by 30% just by avoiding a memory clear). :-) /* Steinar */ -- Homepage: http://www.sesse.net/