Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 295DC1337B88 for ; Mon, 4 Oct 2010 14:39:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 69786-04 for ; Mon, 4 Oct 2010 17:38:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from proton.planetargon.com (proton.planetargon.com [198.145.115.11]) by mail.postgresql.org (Postfix) with ESMTP id BC80D1337B77 for ; Mon, 4 Oct 2010 14:38:57 -0300 (ADT) Received: by proton.planetargon.com (Postfix, from userid 502) id 1BAD182DDBA; Mon, 4 Oct 2010 10:38:54 -0700 (PDT) Received: from [192.168.1.150] (unknown [68.64.144.221]) by proton.planetargon.com (Postfix) with ESMTP id F135382DDB2; Mon, 4 Oct 2010 10:38:47 -0700 (PDT) Subject: Re: MIT benchmarks pgsql multicore (up to 48)performance Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Michael Glaesemann In-Reply-To: Date: Mon, 4 Oct 2010 13:38:33 -0400 Cc: Hakan Kocaman , pgsql-hackers@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <1D0057B0-7151-425C-8096-56836F9AB4BD@seespotcode.net> References: To: Robert Haas X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201010/171 X-Sequence-Number: 171211 On Oct 4, 2010, at 13:13 , Robert Haas wrote: > On Mon, Oct 4, 2010 at 10:44 AM, Hakan Kocaman = wrote: >> for whom it may concern: >> http://pdos.csail.mit.edu/mosbench/ >> They tested with 8.3.9, i wonder what results 9.0 would give. >> Best regards and keep up the good work >> Hakan >=20 > Here's the most relevant bit to us: > The use of lock-free > techniques seems quite interesting; unfortunately, I know next to > nothing about the topic and this paper doesn't provide much of an > introduction. Anyone have a reference to a good introductory paper on > the topic? The README in the postgres section of the git repo leads me to think the = code that includes the fixes it there, if someone wants to look into it = (wrt to the Postgres lock manager changes). Didn't check the licensing. Michael Glaesemann grzm seespotcode net