Hi Michelle,
thanks for the checkin!
I have added an object id class in StateTransitionObj.jdo for
application identity. I'll run the TCK for application identity and
datastore identity overnight and will send the patch for JIRA JDO-13
tomorrow.
Regards,
Michael
Hi, Michael,
I just
Hi, Michael,
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
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
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
Hi Andy,On Jun 7, 2005, at 10:29 AM, Andy Jefferson wrote:Sounds good, thanks. I found that the 6/6 JPOX build ran 10x slowerthan the 6/3 build -- 10 hours to run the TCK. I am running the 6/7build right now, and I'm not sure what the final time will be. At firstit seemed to be running pretty
Hi Craig,
Thanks, does this mean
org.jpox.autoStartMechanism=None
in the properties file?
It does!
See http://www.jpox.org/docs/1_1/performance_tuning.html
--
Andy
Java Persistent Objects JDO - JPOX
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
