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 "John H. Embretsen (JIRA)" <de...@db.apache.org> on 2006/09/21 10:27:22 UTC

[jira] Commented: (DERBY-1568) run derbyall with low memory configuration for 10.2

    [ http://issues.apache.org/jira/browse/DERBY-1568?page=comments#action_12436469 ] 
            
John H. Embretsen commented on DERBY-1568:
------------------------------------------

Regarding comparing 10.2 to 10.1:

There is a difference in how different versions of the test harness interprets and possibly overrides heap size settings. To set non-default heap sizes when running a test suite (or a single test) use the jvmflags system property when starting RunSuite (or RunTest). For example, for running with 16 MB initial heap size and 32 MB maximum heap size, use:

* For 10.1.3.1 (and possibly other 10.1.x versions): 
        -Djvmflags="-ms16m -mx32m"
* For 10.2.1.x and later: 
        -Djvmflags=-Xms16m^-Xmx32m

For more details see DERBY-1614.

> run derbyall with low memory configuration for 10.2
> ---------------------------------------------------
>
>                 Key: DERBY-1568
>                 URL: http://issues.apache.org/jira/browse/DERBY-1568
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.2.1.0
>            Reporter: Kathey Marsden
>             Fix For: 10.2.2.0
>
>
> Run derbyall with  a low memory heap and compare the results to 10.1.  This could help flush out any  memory leaks or increased memory usage in 10.2. I am not sure exactly what the minimum level is to run derbyall on 10.1. It may take some experimentation.
> Good task for the RegressionSearchAndDestroy contest

-- 
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