db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: 0.05% of test fixtures contribute 53% of the total running time!!
Date Tue, 24 Apr 2007 09:01:07 GMT
Øystein Grøvlen <Oystein.Grovlen@Sun.COM> writes:

> Knut Anders Hatlen wrote:
>
>> I once wrote my own test runner which printed the time in milliseconds
>> for each test case, see the attached TimeRunner.java.
>
> Thanks, this is useful.
>
>>
>> Note that testPositionAgressive doesn't always take that much time. I
>> think that test and the other testPosition tests use random offset and
>> length and therefore the variation is high.
>
> While this is true for several of the test cases in BlobClob4BlobTest,
> by looking at the code, I am not able to find anything random in the
> execution of testPositionAgressive.  I will try to run them and see
> what I get.

I think you are correct, there's nothing random in that fixture. It
seems like it started taking a lot more time at revision 530085. I had
run the tests at an earlier revision.

-- 
Knut Anders

Mime
View raw message