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 CA9D33A3AE0 for ; Mon, 25 Oct 2004 02:18:05 +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 84742-06 for ; Mon, 25 Oct 2004 01:17:32 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 05E733A2016 for ; Mon, 25 Oct 2004 02:18:00 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9P1I7tV029891; Sun, 24 Oct 2004 21:18:07 -0400 (EDT) To: Curt Sampson Cc: Kevin Brown , pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some In-reply-to: References: <200410081443.16109.josh@agliodbs.com> <20041009112048.GA665@filer> <27696.1097334448@sss.pgh.pa.us> <20041009203710.GB665@filer> <4859.1097363137@sss.pgh.pa.us> <26467.1098555064@sss.pgh.pa.us> <8438.1098628775@sss.pgh.pa.us> Comments: In-reply-to Curt Sampson message dated "Mon, 25 Oct 2004 09:30:56 +0900" Date: Sun, 24 Oct 2004 21:18:07 -0400 Message-ID: <29890.1098667087@sss.pgh.pa.us> From: Tom Lane 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/405 X-Sequence-Number: 8881 Curt Sampson writes: > I see the OS issues related to mapping that much memory as a much bigger > potential problem. I see potential problems everywhere I look ;-) Considering that the available numbers suggest we could win just a few percent (and that's assuming that all this extra mechanism has zero cost), I can't believe that the project is worth spending manpower on. There is a lot of much more attractive fruit hanging at lower levels. The bitmap-indexing stuff that was recently being discussed, for instance, would certainly take less effort than this; it would create no new portability issues; and at least for the queries where it helps, it could offer integer-multiple speedups, not percentage points. My engineering professors taught me that you put large effort where you have a chance at large rewards. Converting PG to mmap doesn't seem to meet that test, even if I believed it would work. regards, tom lane