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 D770C329F4D for ; Wed, 13 Oct 2004 19:57:53 +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 98492-05 for ; Wed, 13 Oct 2004 18:57:45 +0000 (GMT) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id 9176532AA03 for ; Wed, 13 Oct 2004 19:57:45 +0100 (BST) Received: (from markw@localhost) by mail.osdl.org (8.11.6/8.11.6) id i9DIviQ13537; Wed, 13 Oct 2004 11:57:44 -0700 Date: Wed, 13 Oct 2004 11:57:44 -0700 From: Mark Wong To: pgsql-performance@postgresql.org Cc: neilc@samurai.com, swm@alcove.com.au, Stephen Hemminger Subject: futex results with dbt-3 Message-ID: <20041013115744.A11278@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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/181 X-Sequence-Number: 8657 Hi guys, I have some DBT-3 (decision support) results using Gavin's original futex patch fix. It's on out 8-way Pentium III Xeon systems in our STP environment. Definitely see some overall throughput performance on the tests, about 15% increase, but not change with respect to the number of context switches. Perhaps it doesn't really address what's causing the incredible number of context switches, but still helps. I think I'm seeing what Gavin has, that it seems to solves some concurrency problems on x86 platforms. Here's results without futexes: http://khack.osdl.org/stp/298114/ Results with futexes: http://khack.osdl.org/stp/298115/ Mark