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 72BB532BD7F for ; Thu, 14 Oct 2004 05:29:24 +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 44858-04 for ; Thu, 14 Oct 2004 04:29:22 +0000 (GMT) Received: from smtp111.mail.sc5.yahoo.com (smtp111.mail.sc5.yahoo.com [66.163.170.9]) by svr1.postgresql.org (Postfix) with SMTP id 680A732A9C1 for ; Thu, 14 Oct 2004 05:29:21 +0100 (BST) Received: from unknown (HELO jupiter.black-lion.info) (janwieck@68.80.245.191 with login) by smtp111.mail.sc5.yahoo.com with SMTP; 14 Oct 2004 04:29:20 -0000 Received: from [172.21.8.18] ([192.168.192.101]) (authenticated bits=0) by jupiter.black-lion.info (8.12.10/8.12.9) with ESMTP id i9E4TI94074678; Thu, 14 Oct 2004 00:29:19 -0400 (EDT) (envelope-from JanWieck@Yahoo.com) Message-ID: <416E009F.3010709@Yahoo.com> Date: Thu, 14 Oct 2004 00:29:19 -0400 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Stark Cc: Christopher Browne , pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some References: <200410081443.16109.josh@agliodbs.com> <416DCCFF.70304@Yahoo.com> <871xg25538.fsf@stark.xeocode.com> <416DFDDE.5070600@Yahoo.com> <87sm8i3p4f.fsf@stark.xeocode.com> In-Reply-To: <87sm8i3p4f.fsf@stark.xeocode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/191 X-Sequence-Number: 8667 On 10/14/2004 12:22 AM, Greg Stark wrote: > Jan Wieck writes: > >> Which would require that shared memory is not allowed to be swapped out, and >> that is allowed in Linux by default IIRC, not to completely distort the entire >> test. > > Well if it's getting swapped out then it's clearly not being used effectively. Is it really that easy if 3 different cache algorithms (PG cache, kernel buffers and swapping) are competing for the same chips? Jan > > There are APIs to bar swapping out pages and the tests could be run without > swap. I suggested it only as an experiment though, there are lots of details > between here and having it be a good configuration for production use. > -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #