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

Re: `svn log -v' time inefficiencies

From: Alan Langford <jal_at_ambitonline.com>
Date: 2002-06-13 22:51:54 CEST

At 2002/06/13 15:16 -0500, cmpilato@collab.net wrote:
>It seems kinda Band-aid(tm)-ish to me, but only because of the
>redundancy aspect (we *can* derive that information, it just takes
>time proportional to the size of the changes made to any given
>revision). But if a Band-aid(tm) is what we need, then it's what we

There's an analogy to this in database design. Although a fully normalized
database is Goodness(tm), most production databases have selective
denormalizations to improve performance. You have a property here that has
no proper place in a "pure" schema, but the (re)derivation of the result
requires unacceptable amounts of computation. This is less "caching" than
storing a useful intermediate result where it needs to be used more than once.

>Wah-lah, constant-time answers to "What changed in this revision?"

That's voilą. ;)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 22:53:48 2002

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