db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5471) Stress test for identity columns and sequence seem to be taking longer on trunk compared to 10.8.2.2 RC3
Date Fri, 13 Apr 2012 19:32:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253674#comment-13253674
] 

Mike Matrigali commented on DERBY-5471:
---------------------------------------

I think performance comparisons should always be done on systems with derby supported configurations,
ie. write sync enabled.  We should run the tests again on such hardware, and seems reasonable
to turn off debugging for the comparison.  I agree that I don't understand the difference
in sequence
performance on trunk, it was puzzling at the time.  I don't think mamta has the hardware anymore
that the original test was done, so maybe she can rerun in her new windows environment with
disk sync on and see where we are now.  Need to do this on identity columns to make sure no
degredation has
happened now as expected, given the code should be same in 10.8 and trunk.  For sequences
seems like your other posted results are indicating an 
improvement.  

I would like to see single user comparison numbers on write sync machine also.  If no one
else has time I will add it to my list for testing in any upcoming release.
                
> Stress test for identity columns and sequence seem to be taking longer on trunk compared
to 10.8.2.2 RC3
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5471
>                 URL: https://issues.apache.org/jira/browse/DERBY-5471
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.9.0.0
>         Environment: Windows XP version 2.18
> Genuine Intel(R) CPU T2600 dual core @2.16GHz 2.00GB of RAM 
> $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-201102
> 03_74623 (JIT enabled, AOT enabled)
> J9VM - 20110203_074623
> JIT  - r9_20101028_17488ifx3
> GC   - 20101027_AA)
> JCL  - 20110203_01
>            Reporter: Mamta A. Satoor
>
> I have been trying to run org.apache.derbyTesting.perf.clients.Runner (which provides
ways to stress test sequence generator and identity columns) on trunk and 10.8.2.2 RC3 to
compare the performance and I find that it takes almost double the time for the tests to finish
on trunk. Additionally, the identity column test consistently ran into lock timeouts on trunk.
I am running with insane jars on trunk and 10.8.2.2 RC3. The test in question is not in official
jars for the release candidate so I manually copied them to 10.8.2.2 RC3 environment during
my test(basically copied the entire org.apache.derbyTesting.perf.clients.Runner directory
from trunk to 10.8.2.2 RC3 environment).
> Command to do sequence stress testing is as follows
> java org.apache.derbyTesting.perf.clients.Runner -driver org.apache.derby.jdbc.EmbeddedDriver
-init -load seq_gen -load_opts debugging=1,numberOfGenerators=5,tablesPerGenerator=10,insertsPerTransaction=100,identityTest=0
-gen b2b -threads 10
> Command to do identity column stress testing is as follows
> time java org.apache.derbyTesting.perf.clients.Runner -driver org.apache.derby.jdbc.EmbeddedDriver
-init -load seq_gen -load_opts debugging=1,numberOfGenerators=5,tablesPerGenerator=10,insertsPerTransaction=100,identityTest=1
-gen b2b -threads 10
> An average run on 10.8.2.2 RC3 for sequence stress test is about a minute and 46 secs.
On trunk, on an average it takes 2 and half minutes
> An average run on 10.8.2.2 RC3 for identity stress test is about a minute and 50 secs.
On trunk, on an average it takes 3minsutes and 30 secs. Also, on trunk, this test runs into
lock timeouts.
> I was wondering if this is the right behavior. The performance should be better in trunk
because of pre-allocation of range for sequences and identity columns(which defaults to 20)
but unless I have missed something in my tests, the results don't show the performance improvement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message