Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 53995 invoked from network); 5 Mar 2007 19:27:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Mar 2007 19:27:12 -0000 Received: (qmail 17190 invoked by uid 500); 5 Mar 2007 19:27:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 17162 invoked by uid 500); 5 Mar 2007 19:27:20 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 17153 invoked by uid 99); 5 Mar 2007 19:27:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 11:27:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 11:27:11 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C71A071433C for ; Mon, 5 Mar 2007 11:26:50 -0800 (PST) Message-ID: <28994865.1173122810791.JavaMail.jira@brutus> Date: Mon, 5 Mar 2007 11:26:50 -0800 (PST) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-2327) Reduce monitor contention in LockSet In-Reply-To: <19238286.1171358585504.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2327: -------------------------------------- Derby Info: [Patch Available] > Reduce monitor contention in LockSet > ------------------------------------ > > Key: DERBY-2327 > URL: https://issues.apache.org/jira/browse/DERBY-2327 > Project: Derby > Issue Type: Sub-task > Components: Performance, Services > Affects Versions: 10.3.0.0 > Reporter: Knut Anders Hatlen > Assigned To: Knut Anders Hatlen > Priority: Minor > Attachments: ConcurrentHashMap.diff, derby-2327-1a.diff, derby-2327-1a.stat > > > When multiple threads enter the lock manager, only one can access the hash table in LockSet. To improve scalability on multiple CPUs, it should be possible to have more than one thread accessing the lock table at the same time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.