db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Cordes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1789) 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java
Date Mon, 04 Dec 2006 15:37:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1789?page=comments#action_12455330 ] 
            
Stefan Cordes commented on DERBY-1789:
--------------------------------------

We use the derby.system.durability=test property for doing a kind of bulk database copy (with
data coming out of z/OS DB2).

With the official released version 10.2.1.6 the inserts are 9 times (!) slower that in 10.1.2.2
(370021).
With 10.2 it took 44 minutes, with 10.1 only 5 minutes.

So I can confirm this bug.

(Derby 10.2 did write 31 log files (log31.dat) and 10.1 did, too)

> 'FAIL -- derby.system.durability=test mode seems to be broken.' in store/TestDurabilityProperty.java
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1789
>                 URL: http://issues.apache.org/jira/browse/DERBY-1789
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.2.1.6
>         Environment: Host: 2 X i86pc i386 (AMD Opteron(tm) Processor 250): 2388 MHz,
unknown cache.  2048 Megabytes Total Memory.
> OS: Solaris Nevada snv_43 X86 64 bits - SunOS 5.11 snv_43
> JVM: Sun Microsystems Inc. 1.4.2_05
>            Reporter: Ole Solberg
>            Priority: Minor
>
> Diff says:
> "> FAIL -- derby.system.durability=test mode seems to be broken.
> > -- In this mode one would expect that inserts with autocommit off and on would be
in the same range as syncs are not happening but the difference here seems to be more than
the approximate estimated range.
> > -- Also comparing the time taken to do the inserts without this property set seems
to be in the same range as with this property set.
> > -- Please note this test times inserts and approximate estimates were considered
to report this observation.
> Test Failed.
> "
> Could this be caused by other high load on the machine? Not that I can confirm that this
happended here though.
> Log: http://www.multinet.no/~solberg/public/Apache/10.2.1.1_RC/jvm1.4/testlog/solN+1/436991-derbyall_diff.txt

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

        

Mime
View raw message