You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2007/04/10 17:11:33 UTC

[jira] Updated: (DERBY-2493) Use unsynchronized collections in BackingStoreHashtable

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

Knut Anders Hatlen updated DERBY-2493:
--------------------------------------

    Attachment: derby-2493-hashtable.diff

derby-2493-hashtable.diff replaces the Hashtable in BackingStoreHashtable with a HashMap. Derbyall and suites.All ran successfully (except the tests that also fail in the Tinderbox).

> Use unsynchronized collections in BackingStoreHashtable
> -------------------------------------------------------
>
>                 Key: DERBY-2493
>                 URL: https://issues.apache.org/jira/browse/DERBY-2493
>             Project: Derby
>          Issue Type: Improvement
>          Components: Performance, Store
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: derby-2493-aggregate.diff, derby-2493-aggregate.stat, derby-2493-assert.diff, derby-2493-assert.stat, derby-2493-hashtable.diff
>
>
> BackingStoreHashtable uses a Vector and a Hashtable, but doesn't need the synchronization provided by these classes (I think). Replacing them with ArrayList and HashMap could improve performance for some kinds of operations.

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