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)" <de...@db.apache.org> on 2006/09/22 19:55:22 UTC
[jira] Created: (DERBY-1879) Save meta data related information for
an EmbedResultSet at the plan level instead of the ResultSet level improves
performance.
Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
-------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-1879
URL: http://issues.apache.org/jira/browse/DERBY-1879
Project: Derby
Issue Type: Improvement
Components: JDBC, Performance
Reporter: Daniel John Debrunner
Assigned To: Daniel John Debrunner
Priority: Minor
EmbedResultSet creates and holds references to information that logically is at the plan level, the same for all ResultSet's that use the same prepared plan. Holding this information at the EmbedResultSet hurts performance and memory usage as ResultSet objects are short lived.
Saving the ResultSetMetaData object in the ResultDescription object means a single creation for the lifetime of the plan (shared across connections), rather than once per ResultSet object as needed.
Saving the column name to position mapping added in DERBY-1862 in the ResultDescription has a similar benefit, the map is set up once per prepared plan, not once per executeQuery().
With test changes (will attach patch soon), the performance of the derby1862 test in DERBY-1876 improves by around 15%
--
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
[jira] Resolved: (DERBY-1879) Save meta data related information
for an EmbedResultSet at the plan level instead of the ResultSet level
improves performance.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1879?page=all ]
Daniel John Debrunner resolved DERBY-1879.
------------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Committed revision 450607
> Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1879
> URL: http://issues.apache.org/jira/browse/DERBY-1879
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Performance
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1879_diff.txt
>
>
> EmbedResultSet creates and holds references to information that logically is at the plan level, the same for all ResultSet's that use the same prepared plan. Holding this information at the EmbedResultSet hurts performance and memory usage as ResultSet objects are short lived.
> Saving the ResultSetMetaData object in the ResultDescription object means a single creation for the lifetime of the plan (shared across connections), rather than once per ResultSet object as needed.
> Saving the column name to position mapping added in DERBY-1862 in the ResultDescription has a similar benefit, the map is set up once per prepared plan, not once per executeQuery().
> With test changes (will attach patch soon), the performance of the derby1862 test in DERBY-1876 improves by around 15%
--
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
[jira] Updated: (DERBY-1879) Save meta data related information for
an EmbedResultSet at the plan level instead of the ResultSet level improves
performance.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-1879:
---------------------------------
Derby Categories: [Performance]
> Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1879
> URL: https://issues.apache.org/jira/browse/DERBY-1879
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.1.4
>
> Attachments: derby1879_diff.txt
>
>
> EmbedResultSet creates and holds references to information that logically is at the plan level, the same for all ResultSet's that use the same prepared plan. Holding this information at the EmbedResultSet hurts performance and memory usage as ResultSet objects are short lived.
> Saving the ResultSetMetaData object in the ResultDescription object means a single creation for the lifetime of the plan (shared across connections), rather than once per ResultSet object as needed.
> Saving the column name to position mapping added in DERBY-1862 in the ResultDescription has a similar benefit, the map is set up once per prepared plan, not once per executeQuery().
> With test changes (will attach patch soon), the performance of the derby1862 test in DERBY-1876 improves by around 15%
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1879) Save meta data related information for
an EmbedResultSet at the plan level instead of the ResultSet level improves
performance.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1879?page=all ]
Daniel John Debrunner closed DERBY-1879.
----------------------------------------
> Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1879
> URL: http://issues.apache.org/jira/browse/DERBY-1879
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Performance
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby1879_diff.txt
>
>
> EmbedResultSet creates and holds references to information that logically is at the plan level, the same for all ResultSet's that use the same prepared plan. Holding this information at the EmbedResultSet hurts performance and memory usage as ResultSet objects are short lived.
> Saving the ResultSetMetaData object in the ResultDescription object means a single creation for the lifetime of the plan (shared across connections), rather than once per ResultSet object as needed.
> Saving the column name to position mapping added in DERBY-1862 in the ResultDescription has a similar benefit, the map is set up once per prepared plan, not once per executeQuery().
> With test changes (will attach patch soon), the performance of the derby1862 test in DERBY-1876 improves by around 15%
--
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
[jira] Updated: (DERBY-1879) Save meta data related information for
an EmbedResultSet at the plan level instead of the ResultSet level improves
performance.
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1879?page=all ]
Daniel John Debrunner updated DERBY-1879:
-----------------------------------------
Attachment: derby1879_diff.txt
Patch which implements the two changes described. Needs some of the comments to be fixed.
> Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1879
> URL: http://issues.apache.org/jira/browse/DERBY-1879
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Performance
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Attachments: derby1879_diff.txt
>
>
> EmbedResultSet creates and holds references to information that logically is at the plan level, the same for all ResultSet's that use the same prepared plan. Holding this information at the EmbedResultSet hurts performance and memory usage as ResultSet objects are short lived.
> Saving the ResultSetMetaData object in the ResultDescription object means a single creation for the lifetime of the plan (shared across connections), rather than once per ResultSet object as needed.
> Saving the column name to position mapping added in DERBY-1862 in the ResultDescription has a similar benefit, the map is set up once per prepared plan, not once per executeQuery().
> With test changes (will attach patch soon), the performance of the derby1862 test in DERBY-1876 improves by around 15%
--
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