[
https://issues.apache.org/jira/browse/DERBY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-4807:
--------------------------------------
Attachment: analysis_suitesall.xls
Attaching a spreadsheet that sets out the various test fixtures of the manual
run (starting the java class directly (i.e.. junit.textui.TestRunner) from a
window) vs. my script run (starting the test run(s) for a number of jvms a
scheduled task that kicks off a java program that kicks of a script that kicks
off junit.textui.TestRunner suites.All). Only showing the times for the ibm 1.6
test runs. The numbers are the duration in milliseconds reported by
-Dderby.tests.trace=true junit.textui.TestRunner.
Looking at the data so far, it seems less likely there's a derby bug here.
Still looking into it further. I'll try to use one test next, and I picked
functionTests.tests.memory.TriggerTest (has fixtures that start with 'test5';
they're taking more than a couple of miliseconds, so not too quick, and they
were considerably slower in the 2003 and 2008 runs.)
Some other interesting (?) details:
- the testLDAPConnection fixtures took a great deal more time during the
windows 2003 and 2008 runs.
- the stress multi test took about the same time during each run.
> analyze performance slow-down of suites.All/derbyall combo between Windows XP
> and Windows 2003 and Windows 2008.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4807
> URL: https://issues.apache.org/jira/browse/DERBY-4807
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.6.2.1
> Environment: Windows XP, Windows 2003, Windows 2008, IBM JVM 1.6
> (SR8), 1.5 (SR11) and weme 6.2
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: analysis_suitesall.xls
>
>
> Setting up automated nightly test runs has been troublesome for 10.6 on
> windows because the set of tests (derbyall/suitesall with 3 different jvms)
> that completed within a day on a machine with similar hardware but running XP
> did not complete within a day on a machine running Windows 2008.
> Switching to a machine with windows 2003 appeared to improve matters.
> Switching to a machine with XP, and the test finished.
> Initially, my focus has been to try to get the tests to run consistently, now
> I will be analyzing this further.
> I now have a separate machine that has the 3 OSs loaded on it, and will
> experiment, and gather data, using the 10.6.2 jars so the only difference is
> the OS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
