Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <101668438.1140352587501.JavaMail.jira@ajax.apache.org>
Date: Sun, 19 Feb 2006 13:36:27 +0100 (CET)
From: "Dyre Tjeldvoll (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-938) ContextManager needs to be optimized
In-Reply-To: <1356944242.1139464678485.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-938?page=all ]

Dyre Tjeldvoll updated DERBY-938:
---------------------------------

    Attachment: get.v2.html

New spreadsheet (get.v2.html) that shows the effect of a new version of the patch which doesn't include the getContext() optimization. Seems like there is a substantial benefit to be had from just switching to a non-synchronized container, (note the large reduction in wait time). 

> ContextManager needs to be optimized
> ------------------------------------
>
>          Key: DERBY-938
>          URL: http://issues.apache.org/jira/browse/DERBY-938
>      Project: Derby
>         Type: Improvement
>   Components: Performance
>     Reporter: Dyre Tjeldvoll
>     Assignee: Dyre Tjeldvoll
>     Priority: Minor
>  Attachments: derby-938.diff, derby-938.html, get.html, get.v2.html
>
> ContextManagers are used extensively, particularly to get access to ExcutionContexts and StatementContexts. Optimizing this access should improve overall performance. 

-- 
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