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 35A1352ABE for ; Wed, 13 Jul 2005 13:08:05 -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 83738-01 for ; Wed, 13 Jul 2005 16:07:56 +0000 (GMT) Received: from cmailm2.svr.pol.co.uk (cmailm2.svr.pol.co.uk [195.92.193.210]) by svr1.postgresql.org (Postfix) with ESMTP id 5ED1952A58 for ; Wed, 13 Jul 2005 13:07:54 -0300 (ADT) Received: from modem-2867.leopard.dialup.pol.co.uk ([217.135.155.51] helo=192.168.0.102) by cmailm2.svr.pol.co.uk with esmtp (Exim 4.41) id 1Dsjm6-0001VV-32; Wed, 13 Jul 2005 17:07:54 +0100 Subject: Re: size of cache From: Simon Riggs To: Jean-Max Reymond Cc: pgsql-performance@postgresql.org In-Reply-To: <4b09a0c05071301207d452ace@mail.gmail.com> References: <4b09a0c05071301207d452ace@mail.gmail.com> Content-Type: text/plain Organization: 2nd Quadrant Date: Wed, 13 Jul 2005 17:07:47 +0100 Message-Id: <1121270867.3970.266.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.052 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200507/141 X-Sequence-Number: 13382 On Wed, 2005-07-13 at 10:20 +0200, Jean-Max Reymond wrote: > with my application, it seems that size of cache has great effect: > from 512 Kb of L2 cache to 1Mb boost performance with a factor 3 and > 20% again from 1Mb L2 cache to 2Mb L2 cache. Memory request time is the main bottleneck in well tuned database systems, so your results could be reasonable. > I don't understand why a 512Kb cache L2 is too small to fit the data's > does it exist a tool to trace processor activity and confirm that > processor is waiting for memory ? You have both data and instruction cache on the CPU. It is likely it is the instruction cache that is too small to fit all of the code required for your application's workload mix. Use Intel VTune or similar to show the results you seek. Best Regards, Simon Riggs