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 Wed, 15 Feb 2006 16:15:09 GMT
     [ http://issues.apache.org/jira/browse/DERBY-938?page=all ]

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

    Attachment: get.xhtml

Attaching a spreadsheet that shows the reduction in CPU resulting from optimizing getContext(String)
for StatementContext and ExecutionContext. The load is  single record select, 100000 records
in the table, pageCacheSize=10000, 10 sek warmup time, and 10 min running time. The measurements
are obtained using Sun Performance Analyzer 7.4

While I have accepted the fact that the getContext(String) part of the patch will not make
it into Derby, I would still like to document that there IS a perfomance issue  lurking here,
and I would encourage "the folks that have been working on the product for nearly ten years"
to think about how it can be fixed without violating other important design criteria.

> 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, derby-938.stat, derbyall_report.txt, get.xhtml
>
> 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


Mime
View raw message