db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-938) ContextManager needs to be optimized
Date Thu, 09 Feb 2006 17:45:25 GMT
Thanks for the description of the changes.  I have not looked at the 
patch, just the description so far.  so I have the following question:

I know there is a single point (somewhere in the jdbc entry code) that 
is used to stop
multiple threads from accessing the same connection at the same time,
is it affected by your changes?

Is it true that each context manager is a thread local variable?  With
connection pooling I know that a connection and it's associated context
manager can be executed on a different thread each time it enters
the jdbc stack.

Also what kind of performance gains are you seeing from the change?

Dyre Tjeldvoll (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-938?page=comments#action_12365752 ]

> Dyre Tjeldvoll commented on DERBY-938:
> --------------------------------------
> Hi Dan you are up early. You managed to put in your comment while I was attaching the
description document. Does it address your concern?
>>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
>>ContextManagers are used extensively, particularly to get access to ExcutionContexts
and StatementContexts. Optimizing this access should improve overall performance. 

View raw message