[
http://issues.apache.org/jira/browse/DERBY-815?page=comments#action_12426672 ]
Dyre Tjeldvoll commented on DERBY-815:
--------------------------------------
No I don't see this as urgent for 10.2. Wrt. to the visibility of CliParam in
DRDAConnThread, I think you're making a valid point. However, CliParam was not
added to improve encapsulation or code structure. It is just a utility to avoid
having two containers of (pointers to) Integer/Long objects that were created
and discarded again and again. I actually tried to preserve the existing
program structure as much as possible, ("small incremental changes").
> Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()
> -----------------------------------------------------------------------------
>
> Key: DERBY-815
> URL: http://issues.apache.org/jira/browse/DERBY-815
> Project: Derby
> Issue Type: Sub-task
> Components: Network Server, Performance
> Affects 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
> Assigned To: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.2.0.0
>
> Attachments: d815_regress.diff, d815_regress.java, derby-815.diff,
> derby-815.html, derby-815.v3.diff, derby-815.v3.html, derby-815.v3.stat,
> derby-815.v4.diff, derby-815.v4.stat, derby-815_2.diff,
> derbyall_report.v4.txt, derbyall_report_with_jdk1.4.v3.txt
>
>
> 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
