geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <d...@coredevelopers.net>
Subject Re: Unit/Stress Tests
Date Tue, 03 Aug 2004 19:09:16 GMT
On Aug 3, 2004, at 12:22 PM, David Jencks wrote:

>
> On Aug 3, 2004, at 10:17 AM, David Blevins wrote:
>
>> On Tue, Aug 03, 2004 at 09:19:54AM -0700, David Jencks wrote:
>>> Before we jump off the cliff here, just how long do the stress tests
>>> currently take?
>>
>> Ok, never mind, I retract the idea.  I just ran some comparisons and
>> came out with some interesting numbers.
>>
>> On my 3Ghz WinXP/Cygwin box, these are the numbers I get:
>>
>> $ maven clean; maven -Dmaven.test.failure.ignore=true &> build1.log
>> BUILD SUCCESSFUL
>> Total time: 26 minutes 54 seconds
>>
>> Totalling up the actual "Time elapsed" numbers accounts for only 4.5 
>> minutes (274 seconds) of that time.
>>
>> $ maven clean; maven -Dmaven.test.skip=true &> build2.log
>> BUILD SUCCESSFUL
>> Total time: 6 minutes 49 seconds
>>
>> That's basically a 20 minute difference with only 4.5 minutes
>> reportedly spend on our tests.  What is taking up the other 15
>> minutes?  Is setUp/tearDown not counted in the test time?
>
> If not, the zillions of kernels we create in setUp methods could 
> easily explain the difference.

I would wager that the 15 minutes is spent launching the java vms.  It 
looks like on my machine that there is one vm launched for each unit 
test.  On a very small module, my test time with fork on was 30s and 
with fork off was 10s.

-dain


Mime
View raw message