Let Clock embed a HashMap rather than inherit from Hashtable
------------------------------------------------------------
Key: DERBY-2114
URL: http://issues.apache.org/jira/browse/DERBY-2114
Project: Derby
Issue Type: Improvement
Components: Performance
Affects Versions: 10.2.1.6
Reporter: Dyre Tjeldvoll
Assigned To: Dyre Tjeldvoll
Priority: Trivial
Fix For: 10.3.0.0
Clock currently inherits from Hashtable, but the use of Hashtable is really an
implementation detail that would benefit from being hidden as private member.
All access to the hashtable happens inside sychronized blocks so it is safe to
substitute a HashMap. This change appears to trigger a small increase in
throughput, as measured by the average TPS number obtained by running the
select client from DERBY-1961 repeatedly.
--
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
