db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: !$!% derbyall
Date Thu, 13 Apr 2006 12:44:18 GMT
On my similalry configured machine, debyall takes about half a day to 
run. This contrasts with its behavior last July, when it took maybe 3-4 
hours. It's my impression that derbyall takes significantly longer to 
run this week than it did last week. Here are my unscientific musings:

1) On my machine, I notice that tests take significantly longer if I run 
them under the SecurityManager.
2) I seem to recall that, earlier this year, optimizer modifications 
bloated up the the per-query running time.


David W. Van Couvering wrote:

> <rant on>
> Sorry, but it is so frustrating.  I started a derbyall run at 9 this 
> morning, and it was still running this evening.  My CPU was at 100%, I 
> could get barely any work done, and then my machine hung up, I had to 
> reboot, and the way our harness works you have to start *completely 
> from scratch* -- there is no way to start from the beginning.
> </rant off>
> If I weren't so busy trying to get some this i18n work completed I 
> would do the work of defining a smaller MATS.
> Instead I must sigh and restart the thing all over again.  Hopefully 
> by tomorrow morning it will be completed.   I have two other patches 
> in the queue waiting for machine resources so I can run derbyall for 
> them as well...
> David

View raw message