db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2122) Optimize ContainerLock.isCompatible()
Date Mon, 29 Jun 2009 14:23:47 GMT

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

Dag H. Wanvik updated DERBY-2122:

    Derby Categories: [Performance]

> Optimize ContainerLock.isCompatible()
> -------------------------------------
>                 Key: DERBY-2122
>                 URL: https://issues.apache.org/jira/browse/DERBY-2122
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>             Fix For:
>         Attachments: derby-2122-v1.diff, derby-2122-v1.stat, derby-2122-v2.diff, derby-2122-v2.stat
> The numbers at http://wiki.apache.org/db-derby/Derby1961MethodCalls indicate that ContainerLock.isCompatible()
is called many times per transaction, at least when there are multiple concurrent clients
operating on the same containers. Currently, it looks into a two-dimensional array to find
out whether two locks are compatible. This could be implemented more efficiently, for instance
by having a bit pattern in each ContainerLock object representing which lock types it is compatible

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

View raw message