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] Commented: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()
Date Wed, 18 Jan 2006 19:12:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-815?page=comments#action_12363142 ] 

Dyre Tjeldvoll commented on DERBY-815:
--------------------------------------

>From profiling I have seen that this method has some sub-optimal use of Vectors, and I
am close to submitting a patch for this. But I have not been able to see any unnecessary "decoding".
At first I thought that CodePoint.FDODSC could be skipped when re-executing a statement that
has already been exceuted, but running derbynet(client)mats with suitable instrumentation
showed that an existing statement could receive parameters with different types, and different
lengths. I also observed that these "type transitions" were different when running with the
DB2 driver and the Derby driver (for the same test). 

> Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()
> -----------------------------------------------------------------------------
>
>          Key: DERBY-815
>          URL: http://issues.apache.org/jira/browse/DERBY-815
>      Project: Derby
>         Type: Sub-task
>   Components: Network Server, Performance
>     Versions: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.1.3.0, 10.1.2.2, 10.0.2.2
>     Reporter: Knut Anders Hatlen
>     Assignee: Dyre Tjeldvoll
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> Reported by Kathey Marsden in DERBY-212:
> In reviewing the Network Server Code and profiling there were several
> areas that showed potential for providing performance
> improvement. Functions that need optimizing to prevent unneeded object
> creation and excessive decoding: parseSQLDTA_work()

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