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 Wed, 15 Apr 2009 21:26:14 GMT

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

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

    Attachment: TestInPlaceCompressWithPKViolation.java

I chatted with Mike this morning about the expectations of inplace compress and he felt that
while inplace compress might not return the pages to the operating system, it should recognize
them as free pages after the inplace compress.  I modified my little program to print out
the SpaceTable before the inplace compress and after and then after a regular compress table.
  The program successfully inserts one 3MB Clob and then has 9 failed attempts to insert 3MB
clobs, then does an inplace compress and then a regular compress. Below is the output. After
the inplace compress we only see 18 pages free.  Is that correct?


[C:/kmarsden/repro/derby-4152] java TestInPlaceCompressWithPKViolation
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
The statement was aborted because it would have caused a duplicate key value in a unique or
primary key constraint or un
ique index identified by 'SQL090415141923750' defined on 'TAB'.
*****spaceTable before SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE('APP','TAB',1,1,1)
CONGLOMERATENAME
        |ISIND&|NUMALLOCATEDPAGES   |NUMFREEPAGES        |NUMUNFILLEDPAGES    |PAGESIZE
  |ESTIMSPACESAVING
------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
TAB
        |0     |931                 |0                   |1                   |32768     
|0
*****spaceTable after SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE('APP','TAB',1,1,1)
CONGLOMERATENAME
        |ISIND&|NUMALLOCATEDPAGES   |NUMFREEPAGES        |NUMUNFILLEDPAGES    |PAGESIZE
  |ESTIMSPACESAVING
------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
TAB
        |0     |913                 |18                  |1                   |32768     
|589824
*****spaceTable after SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','TAB',1)
CONGLOMERATENAME
        |ISIND&|NUMALLOCATEDPAGES   |NUMFREEPAGES        |NUMUNFILLEDPAGES    |PAGESIZE
  |ESTIMSPACESAVING
------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
TAB
        |0     |95                  |0                   |1                   |32768     
|0



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