Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <802657229.1246285427395.JavaMail.jira@brutus>
Date: Mon, 29 Jun 2009 07:23:47 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2114) Let Clock embed a HashMap rather than
 inherit from Hashtable
In-Reply-To: <20300563.1164288722011.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik updated DERBY-2114:
---------------------------------

    Derby Categories: [Performance]

> Let Clock embed a HashMap rather than inherit from Hashtable
> ------------------------------------------------------------
>
>                 Key: DERBY-2114
>                 URL: https://issues.apache.org/jira/browse/DERBY-2114
>             Project: Derby
>          Issue Type: Improvement
>    Affects Versions: 10.2.1.6
>            Reporter: Dyre Tjeldvoll
>            Assignee: Dyre Tjeldvoll
>            Priority: Trivial
>             Fix For: 10.3.1.4
>
>         Attachments: derby-2114.currentsize.v1.diff, derby-2114.currentsize.v1.stat, derby-2114.v1.diff, derby-2114.v1.stat, derby-2114.v2.diff, derby-2114.v2.stat
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.