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 54CD73A3BF0 for ; Sun, 24 Oct 2004 15:39:38 +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 49256-04 for ; Sun, 24 Oct 2004 14:39:04 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 82FC43A2BE5 for ; Sun, 24 Oct 2004 15:39:29 +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 i9OEdZio008439; Sun, 24 Oct 2004 10:39:35 -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> Comments: In-reply-to Curt Sampson message dated "Sun, 24 Oct 2004 14:46:16 +0900" Date: Sun, 24 Oct 2004 10:39:35 -0400 Message-ID: <8438.1098628775@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/394 X-Sequence-Number: 8870 Curt Sampson writes: > On Sat, 23 Oct 2004, Tom Lane wrote: >> Seems to me the overhead of any such scheme would swamp the savings from >> avoiding kernel/userspace copies ... > Well, one really can't know without testing, but memory copies are > extremely expensive if they go outside of the cache. Sure, but what about all the copying from write queue to page? >> the locking issues alone would be painful. > I don't see why they would be any more painful than the current locking > issues. Because there are more locks --- the write queue data structure will need to be locked separately from the page. (Even with a separate write queue per page, there will need to be a shared data structure that allows you to allocate and find write queues, and that thing will be a subject of contention. See BufMgrLock, which is not held while actively twiddling the contents of pages, but is a serious cause of contention anyway.) regards, tom lane