[
https://issues.apache.org/jira/browse/DERBY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473517
]
Daniel John Debrunner commented on DERBY-2249:
----------------------------------------------
Not sure it falls into the category of a "basic" performance test, those seem
to be ones that test a specific action, not a broad range of optimizer issues
like this test.
Maybe the split between "perf" and "system" is arbitrary. I've been thinking of
tests like oe (system/oe) as toolkits. They provide building blocks that can be
used a number of ways, as a performance test, as a stress test, as a system
test, etc. Maybe this test is the same. It could be used to compare the
performance of queries against releases, or it could be used to stress the
optimizer by running for several weeks.
Trying to pre-assign specific tests for the code I think is a mistake,implement
one use but allow others.
> Place holder to attach the long running test which will test Derby's improved
> optimizer
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-2249
> URL: https://issues.apache.org/jira/browse/DERBY-2249
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Manjula Kutty
> Assigned To: Manjula Kutty
> Priority: Trivial
> Attachments: build.xml, DERBY-2249_diff.txt, LangTest.zip
>
>
> Will be adding a test for the improved optimizer particularly to test the fix
> for DERBY-805 and DERBY-1205. Once the files are committed will provide a
> link to both of those issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
