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/08/15 22:27:14 UTC
[jira] Commented: (DERBY-766) Improve code generation to handle
5000 unions in a select the union test in largeCodeGen
[ http://issues.apache.org/jira/browse/DERBY-766?page=comments#action_12428218 ]
Daniel John Debrunner commented on DERBY-766:
---------------------------------------------
Update:
Change 1), don't pass in Activation when it can be obtained from another ResultSet
Completed under this issue number.
Change 2) The optimizer costs being passed in are rarely used.
DERBY-1699 improvement entered to address it
Change 3) The closeCleanup method is passed in as null for all result sets in a tree except the top one.
DERBY-1700 improvement entered to address it
Recent work under this issue has been to add generic code to CodeChunk and BCMethod that splits out expressions in the generated code into sub-methods if the generated code is bigger than the 64k limit imposed by the VM. Testing has shown that this increases the number of unions supported in the largeCodeGen test from ~800 to over 5,200. More testing is needed, basically running the split code at a low threshold with derbyall to ensure that the split works in all situations, e.g. split methods when they are overk 2k in size, instead of 64k.
> Improve code generation to handle 5000 unions in a select the union test in largeCodeGen
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-766
> URL: http://issues.apache.org/jira/browse/DERBY-766
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Affects Versions: 10.2.0.0
> Reporter: Kathey Marsden
> Assigned To: Daniel John Debrunner
> Fix For: 10.2.0.0
>
>
> A good incremental improvement for code generation for 10.2 would be to handle 5000 unions in the largeCodeGen test.
> eg. largeUnionSelect(con, viewName, 5000);
> should pass.
--
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