Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 40664 invoked from network); 24 Apr 2007 07:02:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Apr 2007 07:02:45 -0000 Received: (qmail 48357 invoked by uid 500); 24 Apr 2007 07:02:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48332 invoked by uid 500); 24 Apr 2007 07:02:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 48323 invoked by uid 99); 24 Apr 2007 07:02:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 00:02:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 00:02:42 -0700 Received: from d1-emea-10.sun.com (d1-emea-10.sun.com [192.18.2.120]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l3O72ID2002041 for ; Tue, 24 Apr 2007 07:02:21 GMT Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JGZ00901Q612G00@d1-emea-10.sun.com> (original mail from Oystein.Grovlen@Sun.COM) for derby-dev@db.apache.org; Tue, 24 Apr 2007 08:02:18 +0100 (BST) Received: from [192.168.0.5] ([80.202.23.252]) by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JGZ005H7Q7TUPUH@d1-emea-10.sun.com> for derby-dev@db.apache.org; Tue, 24 Apr 2007 08:02:18 +0100 (BST) Date: Tue, 24 Apr 2007 09:02:20 +0200 From: =?ISO-8859-1?Q?=D8ystein_Gr=F8vlen?= Subject: Re: 0.05% of test fixtures contribute 53% of the total running time!! In-reply-to: <462D84E4.8090802@apache.org> Sender: Oystein.Grovlen@Sun.COM To: derby-dev@db.apache.org Message-id: <462DAB7C.7010006@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT References: <462D84E4.8090802@apache.org> User-Agent: Thunderbird 1.5.0.8 (X11/20061204) X-Virus-Checked: Checked by ClamAV on apache.org Daniel John Debrunner wrote: > In a test run (junit-all) of 5,816 fixtures that took 4124 seconds > (~68mins) *three* fixtures took 53% of the total time. > > testPositionAgressive 1564.684 seconds > testNetworkServerSecurityMechanism 497.280 seconds > testTypesInActionStatement 128.928 seconds > > I think testNetworkServerSecurityMechanism is being worked on but is > anyone looking at reducing the time for testPositionAgressive? > > I'll take a look at the testTypesInActionStatement since I added that test. I will take a look at testPosisitionAgressive since I am currently working with the BlobClob4BlobTest. It suprises me a bit that it takes so long time since I do not think I have experience so long run times for the entire BlobClob4BlobTest. Do you have some tips on how to measure the duration of individual test cases. -- �ystein