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 BB9E63A405A for ; Mon, 25 Oct 2004 02:49: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 91342-06 for ; Mon, 25 Oct 2004 01:48:27 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id AA0943A2019 for ; Mon, 25 Oct 2004 02:48:55 +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 i9P1n3E8006099; Sun, 24 Oct 2004 21:49:03 -0400 (EDT) To: Curt Sampson Cc: 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> <29890.1098667087@sss.pgh.pa.us> Comments: In-reply-to Curt Sampson message dated "Mon, 25 Oct 2004 10:32:55 +0900" Date: Sun, 24 Oct 2004 21:49:03 -0400 Message-ID: <6097.1098668943@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/416 X-Sequence-Number: 8892 Curt Sampson writes: > On Sun, 24 Oct 2004, Tom Lane wrote: >> Considering that the available numbers suggest we could win just a few >> percent... > I must confess that I was completely unaware of these "numbers." Where > do I find them? The only numbers I've seen that directly bear on the question is the oprofile results that Josh recently put up for the DBT-3 benchmark, which showed the kernel copy-to-userspace and copy-from-userspace subroutines eating a percent or two apiece of the total runtime. I don't have the URL at hand but it was posted just a few days ago. (Now that covers all such copies and not only our datafile reads/writes, but it's probably fair to assume that the datafile I/O is the bulk of it.) This is, of course, only one benchmark ... but lacking any measurements in opposition, I'm inclined to believe it. regards, tom lane