db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <david.vancouver...@gmail.com>
Subject Re: Performance of in-place upgrade
Date Fri, 05 Feb 2010 00:05:16 GMT
Thanks again, Mike!  Very helpful!

On Thu, Feb 4, 2010 at 3:45 PM, Mike Matrigali <mikem_app@sbcglobal.net>wrote:

> The answer would of course depend on the level of the current db and the
> level of the software you are moving to.
> But as a general rule I would expect "soft" upgrades to almost take no
> time at all, as the purpose of a soft upgrade is to not change anything
> just allow new software to work on old dbs and allow the old software
> also to work.  Since all this happens at boot time it is hard to tell the
> difference between other boot time stuff the db might have to do like
> recovery which is much harder to estimate as it depends on what
> db was doing and how it was shut down.
> So far I don't think even hard upgrades will take very much as I don't
> think any derby release has had a hard upgrade that required any work at
> upgrade
> time on a per row/column basis.  Most hard upgrade work has had to do with
> ddl, so is more dependent on number of ddl like tables, indexes, statements,
> and the like.  This does not mean it won't happen in
> the future, but it would be a last choice in my opinion.  In general we
> have rather looked at supporting both new and old types rather than pay
> a convert cost at upgrade time.
> /mikem
> David Van Couvering wrote:
>> Hi, all.  Yes, I'm now using Derby within the product I'm working on in my
>> new job! :)
>> So, I have some questions.  I'll send separate emails for each ones to
>> keep the threads simpler.
>> I could  have quite a few rows in my table - perhaps up to 100 million.
>>  The table will have about 5 columns.  Do you have a sense of how long it
>> will take to do a soft upgrade of a database of this size?  Is it in the 1-9
>> minute range, 10-20 minutes, 1 hour, multiple hours?  I can test this
>> myself, but I was wondering if anyone could give me a quick ballpark.
>> Thanks,
>> David
>> --
>> David W. Van Couvering
>> http://www.linkedin.com/in/davidvc
>> http://davidvancouvering.blogspot.com
>> http://twitter.com/dcouvering

David W. Van Couvering


View raw message