db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-212) Optimize some specific methods in Network Server to improve performance
Date Wed, 14 Dec 2005 08:35:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-212?page=comments#action_12360406 ] 

Knut Anders Hatlen commented on DERBY-212:

The method buildDB2CursorName() mentioned in the description of this
issue seems to have disappeared from the code. A comment in
DRDAConnThread.parsePKGNAMCSN() says

  // Note: This string is parsed by DRDAStatement.buildDB2CursorName()

but there is no such method in DRDAStatement. There is however a
method called extractPkgcnstknStr() which parses the string returned
by parsePKGNAMCSN() and seems to take a lot of resources.

> Optimize some specific methods in Network Server to improve performance
> -----------------------------------------------------------------------
>          Key: DERBY-212
>          URL: http://issues.apache.org/jira/browse/DERBY-212
>      Project: Derby
>         Type: Improvement
>   Components: Network Server
>     Versions:
>     Reporter: Kathey Marsden
>     Priority: Minor

> 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
> parsePKGNAMCSN()
> parseSQLDTA_work()
> buildDB2CursorName()
> In DDMWriter and DDMReader, use System Routines in 
> java.util.Arrays and System.arrayCopy instead of 
> writing code to do functions like copy arrays and 
> pad strings.

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