db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6708) OOME when running ConstraintCharacteristicsTest with smaller heap
Date Wed, 20 Aug 2014 23:07:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dag H. Wanvik updated DERBY-6708:

    Attachment: derby-6708.diff

Attaching [^derby-6708.diff].

Patch derby-6708. Reduces the number of rows of the fixture testManySimilarDuplicates from
40K to 4K. Removes the use of in-memory database for all fixtures that use it.  In my set-up
(Ubuntu 12.04 64 bits, JDK 8u20) the test now runs fine with -Xmx128M, in ca. 70 seconds with
"derby.system.durability=test". Running regressions.

> OOME when running ConstraintCharacteristicsTest with smaller heap
> -----------------------------------------------------------------
>                 Key: DERBY-6708
>                 URL: https://issues.apache.org/jira/browse/DERBY-6708
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6708.diff
> When I ran suites.All on a device with little memory, so that I needed to reduce the
heap (-Xmx160M), it stopped and failed with an OOME when it came to ConstraintCharacteristicsTest.
> That test uses a memory database in order to speed it up. One of the test cases (testManySimilarDuplicates)
has such a big data set that the database doesn't fit in the heap. It would be good if we
could reduce the memory requirements of the test so that it passes on smaller devices to.
Alternatively, we could add a switch that makes it easy to disable test cases that are known
to have high memory requirements.

This message was sent by Atlassian JIRA

View raw message