[ http://issues.apache.org/jira/browse/DERBY-815?page=comments#action_12366337 ]
Dyre Tjeldvoll commented on DERBY-815: -------------------------------------- Thanks! Yes, that explains a lot. I had a quick look at the tests in derbynetmats, and derbynet/prepStmt.java seems like a good candidate, since the problem appears when using prepared statements with the NetworkServer. I have checked that it isn't listed in either of the .exclude files. If nobody objects, I'll go ahead and add a new test case here. > 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 > Priority: Minor > Fix For: 10.2.0.0 > Attachments: d815_regress.diff, d815_regress.java, d815_regress.stat, > d815_regress_derbyall_report.txt, derby-815.diff, derby-815.stat, derby.log, > derbyall_report.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
