[
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: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Trivial
> Fix For: 10.3.1.4
>
> 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 with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
