You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/07/24 19:55:31 UTC
[jira] Created: (DERBY-2975) DRDAResultSet.setResultSet creates a
new int array to hold type information on every execution.
DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
-----------------------------------------------------------------------------------------------
Key: DERBY-2975
URL: https://issues.apache.org/jira/browse/DERBY-2975
Project: Derby
Issue Type: Improvement
Components: Network Server, Newcomer, Performance
Reporter: Daniel John Debrunner
Priority: Minor
Tracing the code it seems that if a statement is prepared and executed multiple times that new type information stored in DRDAResultSet is created and set every execution.
This wastes cpu cycles as the type information can be determined once at prepare time (I assume) and stored in DRDAPreparedStatement.
It's a little unclear to me the code path for setting the type information, seems to happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
(but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me of a Young Ones episode :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2975) DRDAResultSet.setResultSet creates a
new int array to hold type information on every execution.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-2975:
-------------------------------------
Assignee: (was: Abhilash T.G)
Unassigning due to inactivity.
> DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2975
> URL: https://issues.apache.org/jira/browse/DERBY-2975
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Newcomer, Performance
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> Tracing the code it seems that if a statement is prepared and executed multiple times that new type information stored in DRDAResultSet is created and set every execution.
> This wastes cpu cycles as the type information can be determined once at prepare time (I assume) and stored in DRDAPreparedStatement.
> It's a little unclear to me the code path for setting the type information, seems to happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
> (but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me of a Young Ones episode :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2975) DRDAResultSet.setResultSet creates a
new int array to hold type information on every execution.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-2975:
---------------------------------
Derby Categories: [Newcomer, Performance] (was: [Newcomer])
> DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2975
> URL: https://issues.apache.org/jira/browse/DERBY-2975
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> Tracing the code it seems that if a statement is prepared and executed multiple times that new type information stored in DRDAResultSet is created and set every execution.
> This wastes cpu cycles as the type information can be determined once at prepare time (I assume) and stored in DRDAPreparedStatement.
> It's a little unclear to me the code path for setting the type information, seems to happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
> (but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me of a Young Ones episode :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2975) DRDAResultSet.setResultSet creates a
new int array to hold type information on every execution.
Posted by "Abhilash T.G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhilash T.G reassigned DERBY-2975:
-----------------------------------
Assignee: Abhilash T.G
> DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2975
> URL: https://issues.apache.org/jira/browse/DERBY-2975
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Newcomer, Performance
> Reporter: Daniel John Debrunner
> Assignee: Abhilash T.G
> Priority: Minor
>
> Tracing the code it seems that if a statement is prepared and executed multiple times that new type information stored in DRDAResultSet is created and set every execution.
> This wastes cpu cycles as the type information can be determined once at prepare time (I assume) and stored in DRDAPreparedStatement.
> It's a little unclear to me the code path for setting the type information, seems to happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
> (but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me of a Young Ones episode :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2975) DRDAResultSet.setResultSet creates a
new int array to hold type information on every execution.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648281#action_12648281 ]
Kathey Marsden commented on DERBY-2975:
---------------------------------------
Abhilash, are you still working on this issue? If not could you unassign yourself?
> DRDAResultSet.setResultSet creates a new int array to hold type information on every execution.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2975
> URL: https://issues.apache.org/jira/browse/DERBY-2975
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Newcomer, Performance
> Reporter: Daniel John Debrunner
> Assignee: Abhilash T.G
> Priority: Minor
>
> Tracing the code it seems that if a statement is prepared and executed multiple times that new type information stored in DRDAResultSet is created and set every execution.
> This wastes cpu cycles as the type information can be determined once at prepare time (I assume) and stored in DRDAPreparedStatement.
> It's a little unclear to me the code path for setting the type information, seems to happen as a side effect of writing a SQLDTAGRP which seems a weird place to do it.
> (but then again I have no idea what a SQLDTAGRP is, all these DRDA "names" remind me of a Young Ones episode :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.