[ http://issues.apache.org/jira/browse/DERBY-938?page=comments#action_12366537 ]
Daniel John Debrunner commented on DERBY-938: --------------------------------------------- It's great that you are looking into this, one of my itches is better pure cpu performance for Derby. Suggestions are: 1) As suggested before and I thought was part of your patch, using an unsynchronized collection. 2) Use Integer for context identifiers instead of Strings. I once started some work towards this, moving some context identifiers to a central class to ensure unique numeric identifiers. I wonder if implementing these basic ideas will still show that some language specific changes are needed. If they are let's tackle those separately. > 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
