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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/01/31 01:28:36 UTC
[jira] Commented: (DERBY-216) expand largeCodeGen.java test
[ http://issues.apache.org/jira/browse/DERBY-216?page=comments#action_12364516 ]
Kathey Marsden commented on DERBY-216:
--------------------------------------
I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging.
I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements?
> expand largeCodeGen.java test
> -----------------------------
>
> Key: DERBY-216
> URL: http://issues.apache.org/jira/browse/DERBY-216
> Project: Derby
> Type: Sub-task
> Components: Test
> Reporter: Kathey Marsden
>
> the largeCodeGen test needs to be expanded to include other cases that genreate large amounts of byte code.
> For example:
> large in clause
> large insert statement that inserts many rows
> sql statements with large constant values
> It is best if the verious tests just use a variable that can be bumped higher and higher for testing and if individual cases are isolated.
> Possible approaches, think of ways to make sql statements really big that will take different code paths.
> Look in the code for instances of statementNumHitLimit and create cases that pass through that code. Those cases may pass but the hope is to get rid of these calls in favor of splitting the code in a centralized way, so add the tests to largeCodeGen even if they don't fail.
>
--
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
Re: [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Posted by Kathey Marsden <km...@sbcglobal.net>.
Mike Matrigali wrote:
>I haven't followed the largeCodeGen test much, does it take an extremely
>long time or need a lot of memory? I am not sure what amount of time is
>the cutover from not being appropriate in the nightly suite.
>
largeCodeGen takes about 5 minutes on my laptop, but I have heard
reports that it has taken longer for others. I am not sure what the
cutoff should be.
Kathey
Re: [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Posted by Manjula G Kutty <ma...@gmail.com>.
Mike Matrigali wrote:
>I haven't followed the largeCodeGen test much, does it take an extremely
>long time or need a lot of memory? I am not sure what amount of time is
>the cutover from not being appropriate in the nightly suite. Otherwise
>we should just have add it somewhere else.
>
>I have run the large data test recently, and I think it took 6 hours and
>17gb on a 1.8 laptop. So far I have not made it through a whole suite
>(basically I have only had overnight free on the machine and it has
>not finished). It would be nice if when this test succeeds if it
>dropped it's tables so you would not be left with 17gb in the test
>directory.
>
>If anyone has the resources to run the suite repeatedly, that would
>great. It now will catch some serious blob/clob regressions we have
>had in the past.
>
>Kathey Marsden (JIRA) wrote:
>
>
>
>> [ http://issues.apache.org/jira/browse/DERBY-216?page=comments#action_12364516 ]
>>
>>Kathey Marsden commented on DERBY-216:
>>--------------------------------------
>>
>>I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging.
>>
>>I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements?
>>
>>
>>
>>
>>
>>
>>>expand largeCodeGen.java test
>>>-----------------------------
>>>
>>> Key: DERBY-216
>>> URL: http://issues.apache.org/jira/browse/DERBY-216
>>> Project: Derby
>>> Type: Sub-task
>>> Components: Test
>>> Reporter: Kathey Marsden
>>>
>>>
>>
>>
>>>the largeCodeGen test needs to be expanded to include other cases that genreate large amounts of byte code.
>>>For example:
>>> large in clause
>>> large insert statement that inserts many rows
>>> sql statements with large constant values
>>>It is best if the verious tests just use a variable that can be bumped higher and higher for testing and if individual cases are isolated.
>>>Possible approaches, think of ways to make sql statements really big that will take different code paths.
>>>Look in the code for instances of statementNumHitLimit and create cases that pass through that code. Those cases may pass but the hope is to get rid of these calls in favor of splitting the code in a centralized way, so add the tests to largeCodeGen even if they don't fail.
>>>
>>>
>>>
>>
>>
>
>
>
Hi Mike,
I can run the test on one of my machines which is about 2G RAM and
~20GB disk space. Will let you know the results
Thanks
Manjula
Re: [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Posted by Mike Matrigali <mi...@sbcglobal.net>.
ok, looks like it belongs in that suite. I just wanted to make sure
putting stuff in this suite is the exception. Even with this test it
sounds like it would be nice if the 1st part was a standard test and
the problem query was in this suite.
Daniel John Debrunner wrote:
> Mike Matrigali wrote:
>
>
>>I haven't followed the largeCodeGen test much, does it take an extremely
>>long time or need a lot of memory? I am not sure what amount of time is
>>the cutover from not being appropriate in the nightly suite. Otherwise
>>we should just have add it somewhere else.
>
>
> It drags my latop with 1Gb of memory to a halt, due to large memory
> usage. I'm not sure how long it takes, at least 15mins, I usually kill
> it as I have already gathered what I need to know from the first portion
> of it. In fact it's the very last query that takes the time. It maybe
> that once I fix some of the code generation issues the test can be moved
> into the standard language suite.
>
> Dan.
>
>
>
Re: [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Posted by Daniel John Debrunner <dj...@apache.org>.
Mike Matrigali wrote:
> I haven't followed the largeCodeGen test much, does it take an extremely
> long time or need a lot of memory? I am not sure what amount of time is
> the cutover from not being appropriate in the nightly suite. Otherwise
> we should just have add it somewhere else.
It drags my latop with 1Gb of memory to a halt, due to large memory
usage. I'm not sure how long it takes, at least 15mins, I usually kill
it as I have already gathered what I need to know from the first portion
of it. In fact it's the very last query that takes the time. It maybe
that once I fix some of the code generation issues the test can be moved
into the standard language suite.
Dan.
Re: [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Posted by Mike Matrigali <mi...@sbcglobal.net>.
I haven't followed the largeCodeGen test much, does it take an extremely
long time or need a lot of memory? I am not sure what amount of time is
the cutover from not being appropriate in the nightly suite. Otherwise
we should just have add it somewhere else.
I have run the large data test recently, and I think it took 6 hours and
17gb on a 1.8 laptop. So far I have not made it through a whole suite
(basically I have only had overnight free on the machine and it has
not finished). It would be nice if when this test succeeds if it
dropped it's tables so you would not be left with 17gb in the test
directory.
If anyone has the resources to run the suite repeatedly, that would
great. It now will catch some serious blob/clob regressions we have
had in the past.
Kathey Marsden (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-216?page=comments#action_12364516 ]
>
> Kathey Marsden commented on DERBY-216:
> --------------------------------------
>
> I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging.
>
> I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements?
>
>
>
>
>>expand largeCodeGen.java test
>>-----------------------------
>>
>> Key: DERBY-216
>> URL: http://issues.apache.org/jira/browse/DERBY-216
>> Project: Derby
>> Type: Sub-task
>> Components: Test
>> Reporter: Kathey Marsden
>
>
>>the largeCodeGen test needs to be expanded to include other cases that genreate large amounts of byte code.
>>For example:
>> large in clause
>> large insert statement that inserts many rows
>> sql statements with large constant values
>>It is best if the verious tests just use a variable that can be bumped higher and higher for testing and if individual cases are isolated.
>>Possible approaches, think of ways to make sql statements really big that will take different code paths.
>>Look in the code for instances of statementNumHitLimit and create cases that pass through that code. Those cases may pass but the hope is to get rid of these calls in favor of splitting the code in a centralized way, so add the tests to largeCodeGen even if they don't fail.
>>
>
>