On Mar 22, 2007, at 23:18, Kylo Ginsberg wrote:
> We've just converted a cvs repository to svn, and the resultant
> repository is 5 GB with about 79k revs. A number of cvs users were
> accustomed to using TortoiseCVS to view revision graphs of salient
> files. Of course, this is dead easy and lightning fast with cvs since
> every file's genealogy is represented in a single file in the
> repository. TortoiseSVN will produce revision graphs, but since that
> requires parsing the log history for the entire repository, it is
> impractically slow to put it mildly.
>
> Although I reference the Tortoise guis as examples, my real questions
> are wrt subversion proper:
> * Are changes that could enable rapid construction of revision graphs
> on the svn future feature list? I imagine this would be quite an
> undertaking, but it can't hurt to ask.
> * Are there 3rd party scripts that will cook up revision graphs, or
> perhaps, a database which could be queried dynamically to make
> revision graphs? I'm imagining a tool that could be run nightly to
> build the database indices.
> * We're on fsfs now, but would the performance be dramatically
> different with bdb?
I don't know if any of the existing tools do this, but it sounds to
me like it should be possible for a post-commit hook to record
relevant information about the commit in a database, and for a
revision graph maker to query that database more quickly than
querying the repository directly.
I don't have experience with revision graphs... what does one look
like? Can you send me a sample?
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 23 05:39:28 2007