Hi Nick, The next release fixes the empty commit problem that added many needless lines to the recovery. This improves recovery log performance quite significantly.
Thanks, Robert On 1/18/08 6:19 AM, "Nick Smith" <[EMAIL PROTECTED]> wrote: > Dear Sequoia Users, > > We currently use Apache Derby for the backends in our distributed > Sequoia 2.10.9 cluster and Hypersonic for the Sequoia recovery log. > > Now we hear that their have been problems with HsqlDb in productive > environments and also of the suggestions to limit memory usage via the > URL settins (which we have included in our environment). Therefore we > would like to move the Recovery Log to Derby. > > My question is : does anyone use Derby for the Recovery Log. If so, > how do you configured the database columns and keys in the VDB XML? > I'm asking this as we have critical problem that Derby can take hours > to check a reasonably sized (200,000 rows) recovery log... > > Many Thanks in Advance, > > Nick > > p.s. Does anyone know if the upcoming 2.10.10 release will still insert > select statements into the recovery log? Our applications does 98% > selects and 2% inserts/updates... > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia -- Robert Hodges, CTO, Continuent, Inc. Email: [EMAIL PROTECTED] Mobile: +1-510-501-3728 Skype: hodgesrm _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
