db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2328) Reduce monitor contention in SinglePool
Date Mon, 19 Feb 2007 14:44:05 GMT

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

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

    Attachment: derby-2328.stat
                derby-2328.diff

derby-2328.diff removes the Hashtable in SinglePool. Derbyall and the JUnit tests passed on
Solaris 10/JDK6.

Description of the changes:
  - New method in LockFactory: createCompatibilitySpace()
  - New (almost empty) interface CompatibilitySpace to be returned from createCompatibilitySpace()
  - LockSpace implements CompatibilitySpace and is returned by SinglePool.createCompatibilitySpace()
  - SinglePool no longer extends Hashtable. Now it casts the supplied compatibility space
object to LockSpace and uses it directly.
  - Modified signatures of all methods/variables that used compatibility spaces (Object ->
CompatibilitySpace)
  - Modified code that assumed compatibility space objects were transaction objects (virtual
lock table and code that locked an object with the transaction as lock group)
  - Code that tested space1.equals(space2) was changed to (space1 == space2)

Because of the signature changes the patch grew quite big. Reviews would be greatly appreciated.
Thanks.

> 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: derby-2328.diff, derby-2328.stat, 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.


Mime
View raw message