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/01/10 00:07:48 UTC
[jira] Created: (DERBY-806) One each deleted or updated from a heap
row a new RowPosition object is created.
One each deleted or updated from a heap row a new RowPosition object is created.
--------------------------------------------------------------------------------
Key: DERBY-806
URL: http://issues.apache.org/jira/browse/DERBY-806
Project: Derby
Type: Improvement
Components: Performance, Store
Versions: 10.2.0.0
Reporter: Daniel John Debrunner
Priority: Minor
See the new RowPosition in GenericConglomerateController.delete and replace. The fetch methods also have new RowPosition calls but in general these calls are not made for scans.
Can a single RowPosition object be re-used across the life of the query?
In general Derby should try to avoid creating objects per row in any statement as the gc overhead when operating on a large number of rows can be high.
--
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-806) One each deleted or updated from a heap
row a new RowPosition object is created.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-806:
--------------------------------
Derby Categories: [Performance]
> One each deleted or updated from a heap row a new RowPosition object is created.
> --------------------------------------------------------------------------------
>
> Key: DERBY-806
> URL: https://issues.apache.org/jira/browse/DERBY-806
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assignee: Mike Matrigali
> Priority: Minor
> Fix For: 10.3.1.4
>
>
> See the new RowPosition in GenericConglomerateController.delete and replace. The fetch methods also have new RowPosition calls but in general these calls are not made for scans.
> Can a single RowPosition object be re-used across the life of the query?
> In general Derby should try to avoid creating objects per row in any statement as the gc overhead when operating on a large number of rows can be high.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-806) One each deleted or updated from a
heap row a new RowPosition object is created.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali reassigned DERBY-806:
------------------------------------
Assignee: Mike Matrigali
> One each deleted or updated from a heap row a new RowPosition object is created.
> --------------------------------------------------------------------------------
>
> Key: DERBY-806
> URL: https://issues.apache.org/jira/browse/DERBY-806
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
> Priority: Minor
>
> See the new RowPosition in GenericConglomerateController.delete and replace. The fetch methods also have new RowPosition calls but in general these calls are not made for scans.
> Can a single RowPosition object be re-used across the life of the query?
> In general Derby should try to avoid creating objects per row in any statement as the gc overhead when operating on a large number of rows can be high.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-806) One each deleted or updated from a heap
row a new RowPosition object is created.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-806:
---------------------------------
Fix Version/s: 10.3.0.0
Rather than allocating a scratch RowPosition for every delete/replace/fetch,
changed to use a single copy of a RowPosition allocated on demand per
openGenericConglomerateController. If multiple calls to delete, replace,
and/or fetch are made in the same open controller only one of these objects
will be allocated.
Fixed in checkin :
m2_ibm15:43>svn commit
Sending java\engine\org\apache\derby\impl\store\access\conglomerate\GenericConglomerateController.java
Sending java\engine\org\apache\derby\impl\store\access\conglomerate\GenericScanController.java
Sending java\engine\org\apache\derby\impl\store\access\conglomerate\OpenConglomerateScratchSpace.java
Transmitting file data ...
Committed revision 535878.
> One each deleted or updated from a heap row a new RowPosition object is created.
> --------------------------------------------------------------------------------
>
> Key: DERBY-806
> URL: https://issues.apache.org/jira/browse/DERBY-806
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> See the new RowPosition in GenericConglomerateController.delete and replace. The fetch methods also have new RowPosition calls but in general these calls are not made for scans.
> Can a single RowPosition object be re-used across the life of the query?
> In general Derby should try to avoid creating objects per row in any statement as the gc overhead when operating on a large number of rows can be high.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-806) One each deleted or updated from a
heap row a new RowPosition object is created.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-806.
----------------------------------
Resolution: Fixed
> One each deleted or updated from a heap row a new RowPosition object is created.
> --------------------------------------------------------------------------------
>
> Key: DERBY-806
> URL: https://issues.apache.org/jira/browse/DERBY-806
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Store
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Mike Matrigali
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> See the new RowPosition in GenericConglomerateController.delete and replace. The fetch methods also have new RowPosition calls but in general these calls are not made for scans.
> Can a single RowPosition object be re-used across the life of the query?
> In general Derby should try to avoid creating objects per row in any statement as the gc overhead when operating on a large number of rows can be high.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.