db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4152) mailjdbc test database grows very fast with 10.5
Date Fri, 17 Apr 2009 15:22:15 GMT

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

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

    Attachment: derby-4152_quick_change_to_stop_pk_violation_diff.txt

Sorry attached this to the wrong issue initially.

My trunk run with the small change to eliminate the pk contraint violations has been running
more than 24 hours and I have seen no significant growth with my database size ranging from
32MB - 80MB and the size going up and down as it runs.

I've attached the test diff for reference (derby-4152_quick_change_to_stop_pk_violation_diff.txt).
This is not for commit, but just provides context for the test run.

So since it seems that the pk constraint violations are the only cause of growth in the test
on trunk, and I guess it follows that the 10.5 run was either seeing more pk constraint violations
or was growing more on the same event, although that was not apparent from my small test case.

Next I'll go back to the original behavior and change the test to record more information
on the pk constraint violations, including size of the blob and space table printout and then
compare the trunk and 10.4 runs.
[ Show ยป ]
Kathey Marsden added a comment - 17/Apr/09 08:19 AM My trunk run with the small change to
eliminate the pk contraint violations has been running more than 24 hours and I have seen
no significant growth with my database size ranging from 32MB - 80MB and the size going up
and down as it runs. I've attached the test diff for reference (derby-4152_quick_change_to_stop_pk_violation_diff.txt).
This is not for commit, but just provides context for the test run. So since it seems that
the pk constraint violations are the only cause of growth in the test on trunk, and I guess
it follows that the 10.5 run was either seeing more pk constraint violations or was growing
more on the same event, although that was not apparent from my small test case. Next I'll
go back to the original behavior and change the test to record more information on the pk
constraint violations, including size of the blob and space table printout and then compare
the trunk and 10.4 runs.




> 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: derby-4152_quick_change_to_stop_pk_violation_diff.txt, 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.


Mime
View raw message