[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: When to use Berkeley transactions.

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-02-21 18:40:59 CET

Branko Čibej <brane@xbc.nu> writes:
> I'd say create a branch and do one of the simple modifications (nodes,
> changes, representations, revisions, uuids), and test. If it looks fine,
> move on to strings and test. Then test. After that, test some more. In
> the meantime, while the stress tests are running, read the BDB
> documentation again. After that, test again. Then ask people to pull the
> sources off that branch and test.
> Finally, merge to trunk and pray. :-)


Unless we face an unacceptable performance problem that cannot be
solved some other way, though, I doubt we'll see this before 1.0. At
least, I know I sure don't have time to be rewriting our fs locking
guarantees at the moment, and we've already seen how much gain can be
got through much simpler changes to calling txn_checkpoint.

Not trying to blow your ideas off, just being realistic (I think)
about resources.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 21 19:14:59 2003

This is an archived mail posted to the Subversion Dev mailing list.