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

Re: Switching off file compression for JPEGs in the repository

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2004-11-18 17:42:53 CET

Cassimatis, Jim wrote:

>Mike,
>Below are the results of my observations, which should answer all
>of your questions. However, so that we have a frame of reference
>I also timed how long it took to transfer the same 1GB file between
>client and server directly via the network by using windows drag and drop.
>The results were significantly less, which suggests to me that adding
>Subversion tuning options for large files should results in significant
>performance gains. Also, the time was significantly longer for the
>commit (1h25mins), so the binary differencing algorithm must be the main
>performance bottleneck, probably stage 4 of the commit. See below for more
>information.
>
>

Hi Jim, thanks for posting those timings. They do seem to indicate that
there are times when lots of CPU is being used either on the client or
the server, and that at those times no network comms is happening, which
is consistent with the client or server doing binary diffs.

>File specifications:
>Size 1,322,282KB
>Type zip file
>Contents 659 Paint Shop Pro tga files
>
>

A problem with storing zip files is that, due to the way zip compression
works, if you change some part of a file in the zip, sometimes the
entire zip will be changed, and so Subversion will think the whole thing
has changed. Could you store something other than a zip file? For
example, if you stored each TGA file individually in a directory, only
the files that had actually changed would get checked in.

Cheers,
Mike.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 17:43:36 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.