Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <16959071.1171454767122.JavaMail.jira@brutus>
Date: Wed, 14 Feb 2007 04:06:07 -0800 (PST)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2328) Reduce monitor contention in
 SinglePool
In-Reply-To: <11688225.1171358765969.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-2328:
--------------------------------------

    Attachment: unused.diff

LanguageConnectionContext has a method called getLockSpace(int) which creates a compatibility space, but the method is not used. unused.diff removes the method so that it doesn't complicate things when the use of compatibility space objects changes. All the tests passed.

> Reduce monitor contention in SinglePool
> ---------------------------------------
>
>                 Key: DERBY-2328
>                 URL: https://issues.apache.org/jira/browse/DERBY-2328
>             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: unused.diff
>
>
> When multiple threads enter the lock manager, there might be contention on SinglePool's monitor. The contention should be reduced in order to improve scalability.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.