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

Kathey Marsden updated DERBY-4152:
----------------------------------

    Attachment: insertMailSummary.txt

Understanding the primary key violations ended up to be an adventure.   I am 
attaching insertMailSummary.txt for those who are interested. Thanks to Myrna 
for helping me with this.  I made the short term change described in this 
document to see if there is other growth besides DERBY-691 on trunk and have 
been running for a few hours without noticing any significant growth.

I still have no clue as to what's different between 10.5 and 10.4.


> mailjdbc test database  grows very fast with 10.5
> -------------------------------------------------
>
>                 Key: DERBY-4152
>                 URL: https://issues.apache.org/jira/browse/DERBY-4152
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.5.1.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows 2000 x86-32 
> jvmwi3260-200811
> 05_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> Windows 2000 5.00.2195 /Service pack 4
> 4 CPU 3.00GHz
>            Reporter: Kathey Marsden
>            Priority: Critical
>         Attachments: insertMailSummary.txt, 
> TestInPlaceCompressWithPKViolation.java, 
> TestInPlaceCompressWithPKViolation.java
>
>
> When I ran the mailjdbc test on 10.5.1.0 RC I found that the mailsdb database 
> grew to 16GB after two days.  On 10.4.2.0  on the same machine with the same 
> configuration (no derby.properties) it grew to only 1.7GB after 7 days.  Both 
> were sane builds.
> This is with the embedded configuration:
> java org.apache.derbyTesting.system.mailjdbc.MailJdbc embedded

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to