> Hi, I'm proposing to use Subversion as the backend version control
> system on a project but am having some performance issues,
> specifically in the area of large binary file versioning..
>
> There seem to be 2 kinds of problem:
>
> 1) The local working area is large.
> The pristine local copy doubles the size of the working area, I
> notice there's been some discussion of optionally applying
> compression to help this.
>
> 2) Commit times are very slow:
> for a local disk commit a 650MB file took 7:30s using 1.3.1. Using
> 1.5x this took 6:30s.
> One issue with this is that there seems to be unnecessary delta
> calculations that occur during the commit operation, I'm sure there
> are other issues also.
If you're using large, binary files, then you're probably not interested in
merging or diff output.
Maybe fsvs (fsvs.tigris.org) can help you a bit better:
- it doesn't has the .svn-directories,
- it sends the full-text to the repository; so it trades network bandwidth
against cpu usage. (currently, will be optimized later)
- when checking for modifications it does MD5 over block of about 128kB, and
quits the verification if the first difference is found (less data read
than in svn).
If you find it usable (or have change requests), drop a message on the users@
or dev@-list.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 15 07:29:16 2006