Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Tue, 07 Jun 2005 11:06:45 -0700
From: Michelle Caisse <Michelle.Caisse@sun.com>
Subject: Re: JIRA JDO-13
In-reply-to: <42A5DDC5.7060106@spree.de>
To: jdo-dev@db.apache.org
Message-id: <42A5E235.809@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2)
 Gecko/20040803
References: <42A4825D.7020507@spree.de> <42A5D765.3070509@spree.de>
 <42A5D8BD.4050307@sun.com> <200506071829.31238.andy@jpox.org>
 <42A5DDC5.7060106@spree.de>

Michael,

That sounds like a useful experiment.  I think Derby's performance is 
generally supposed to be good, though.  I don't know how Craig wants to 
prioritize this relative to our other issues.

-- Michelle

Michael Watzek wrote:

> Hi Michelle,
>
> I still use JPOX 1.1.0-beta-3. One TCK run takes about 2 hours. So I'm 
> confident that the two runs will finish overnight :-).
>
> Does it make sense to use MySQL instead of Derby - just to make sure 
> it's not Derby slowing down the performance? We have to adapt the 
> schema files, the URL and the driver name in jdori.properties, and the 
> classpath.
>
> Regards,
> Michael
>
>
> Andy Jefferson wrote:
>
>>> Sounds good, thanks.  I found that the 6/6 JPOX build ran 10x slower
>>> than the 6/3 build -- 10 hours to run the TCK.  I am running the 6/7
>>> build right now, and I'm not sure what the final time will be.  At 
>>> first
>>> it seemed to be running pretty quickly, but now that it's doing the
>>> fieldtypes tests, it is very slow.  So you may want to use an older 
>>> JPOX
>>> build if you hope to get both application and datastore identity 
>>> done in
>>> one night!
>>
>>
>>
>> Hi Michelle,
>> have you got "org.jpox.autoStartMechanism" set to anything in 
>> particular ? The fact that things slow down is symptomatic of JPOX 
>> progressively loading up all of the classes that it has ever 
>> encountered during its lifetime with the DB schema (JPOX_TABLES 
>> table) that it connects to. So with each test, it finds more classes 
>> and so loads up the MetaData of the previous ones, plus the new ones. 
>> If you set this property to "None" it will start from scratch each 
>> time (and so not go off an load up other classes not used in that 
>> test). The log would tell you what is taking the time
>>
>> Nothing significant has changed in the period you mention (AFAIK) and 
>> I see no change in runtime speed here on our unit tests.
>>
>>
>
>