Optimize ContainerLock.isCompatible()
-------------------------------------
Key: DERBY-2122
URL: http://issues.apache.org/jira/browse/DERBY-2122
Project: Derby
Issue Type: Improvement
Components: Store
Affects Versions: 10.2.1.6
Reporter: Knut Anders Hatlen
Assigned To: Knut Anders Hatlen
Priority: Trivial
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
