After reading the documentation that generally describes how files in
SVN are stored (by storing diffs and references to previous versions),
and after doing some poking around in the files created in a
filesystem-type repository, I've begun wondering about how SVN scales.
Suppose I have a file added to subversion at revision 1, and it is
changed 5000 times, with each change committed individually. When I
checkout revision 5001 of that file from subversion, does subversion
have to reconstruct this file by examining every change in sequence from
revision 1? Will this result in a substantially increased checkout time
to reconstruct this file to its proper revision?
There is obviously a question aimed at scaling. In a large system, if
the above scenario is true, there exists the possibility of coming to a
grinding halt with many files changed over many revisions. Merely
checking out a project would be a fairly intensive operation.
I'm sure I am missing something. I was hoping some of the svn gurus out
there could educate me as to how subversion handles this.
Thanks!
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 23 15:07:18 2005