Re: Performance regressions

2006-01-21 Thread Ole Solberg
Kathey Marsden wrote: Ole Solberg wrote: Knut Anders Hatlen wrote: I guess the increase is explained by this. A comment in the JIRA issue on an expected increase in execution time for the test would be good though. It seems like *derby.locks.waitTimeout* might help here, but in

[jira] Resolved: (DERBY-757) java.lang.NullPointerException can occur while scanning for global id in the transaction table under heavey load.

2006-01-21 Thread Mike Matrigali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-757?page=all ] Mike Matrigali resolved DERBY-757: -- Fix Version: 10.2.0.0 10.1.2.2 Resolution: Fixed svn 371085 is the merge of the fix from trunk to 10.1.

Re: Cleaning up test failures

2006-01-21 Thread Mike Matrigali
I like Regression Test Failure best of those so far. As others said didn't really like DerbyAll as it might change names. David W. Van Couvering wrote: I don't like Nightly as it excludes Weekly and Tinderbox regression tests I would replace Nightly Test Failure with Regression Test Failure,

Re: [jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

2006-01-21 Thread Mike Matrigali
Do you happen to know why it works on windows? Is the file lock behavior different, or is the old windows-only locking method automatically kicking in? Suresh Thalamati (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-700?page=comments#action_12363492 ] Suresh Thalamati

Re: Performance regressions

2006-01-21 Thread Mike Matrigali
Sorry about that, I will look and see if there is anything I can do. I never thought about performance as the additional testing was so minimal, but as Kathy pointed out the issue is most likely the default wait time for a lockout tends to be relatively long when compared to the execution time of

Re: Performance regressions

2006-01-21 Thread Ole Solberg
Knut Anders Hatlen wrote: Ole Solberg [EMAIL PROTECTED] writes: . . You're right, the storetests suite has had about 800% for a long time. Just for your information, the tinderbox tests that my stress testing interfered with were revision 370531 (913%) and 370662 (940%). What do these

Re: Discussion of how to map the recovery time into Xmb of log --Checkpoint issue

2006-01-21 Thread Raymond Raymond
Mike, thank you for you comments. They really help me a lot. I would like to make more discussion on the issue. RR2. During initilization of Derby, we run some measurement that RR determines the performance of the system and maps the RR recovery time into some X megabytes of log.

Re: [jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

2006-01-21 Thread Suresh Thalamati
On windows old lock mechanism(if a file is open, it can not be deleted until it is closed..) is used always to prevent the dual boot of the same database, that is why it works fine even with multiple class loaders. Java File lock mechanism is used only on systems where one can delete the

Re: Cleaning up test failures

2006-01-21 Thread Andrew McIntyre
On Jan 21, 2006, at 9:22 AM, Mike Matrigali wrote:I like Regression Test Failure best of those so far. As others said didn't really like DerbyAll as it might change names. Since you, Kathey, and David all like that name, I've updated the name in JIRA.andrew