Cassimatis, Jim wrote:
>Yes, I have a specific problem. The problem is that we have some
>very large JPEGs (around 1GB) and the time taken to check
>them in is very long (more than an hour) so if I could prevent
>Subversion from running the file through it's binary differencing
>algorithm I imagine it would check-in much more quickly.
>
>
>
Is the problem with adding new files, or checking in new versions of
existing files? When things are slow, during the hour-long operation,
what's happening on the client and server machines? If you're using
Windows, you can use Task Manager to look at CPU and network usage
(right click the task bar at the bottom of the screen and choose Task
Manager).
It sounds like you might be trying to do stuff that Subversion isn't
very good at -- for instance did you know that a working copy for 1GB of
files will actually take up 2GB of disk space on the client? This is
because Subversion stores a pristine copy of each file the client
checked out, so it can do offline diff and revert, and send diffs up to
the server when a file change is checked in.
Subversion doesn't (yet) have any tuning options to help it handle large
files. Maybe we need a FAQ section on this kind of thing.
Cheers,
Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 17 06:17:07 2004