db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-938) ContextManager needs to be optimized
Date Sun, 19 Feb 2006 12:36:27 GMT
     [ 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:
For more information on JIRA, see:

View raw message