Kevin Radke wrote:
> I'm using TortoiseSVN 1.5.3 with a Subversion 1.5.2 server running on
> Windows Server 2003 under Apache 2.2.9 using http:// as the protocol.
>
> In testing the commit of large files (>4G), I noticed something odd.
>
> TortoiseSVN appears to be showing the "xxx MBytes transferred, at yyy
> kBytes/s" rate based
> upon how fast Subversion is creating the transaction on the client
> disk. It doesn't appear to
> represent any network activity rates or the actual transfer of data to
> the server. (or
> at least the first numbers it shows)
>
> In the case of a large 4G file, Subversion spends a significant time
> doing disk I/O before
> sending any network data to the server. All the time during this
> operation, TortoiseSVN
> says it is transferring 11000+ kBytes/s, even though a network monitor
> shows no real
> traffic to the server.

Not really: the transfer rates are passed from the neon library (in case
for http transfers). And neon is the DAV library with not connection to
local disks. So it would be highly unlikely that the transfer rates did
not indicate real network transfer.

Make sure your network monitor is working correctly.

But even if somehow this would be wrong as you suggested: you'd have to
report this on the svn mailing list since that data is passed from the
svn library to the clients - TSVN only shows the data it gets.

>
> (For me the transaction then fails on files >2G with an apache 413
> Request Entity Too Large
> error, but I get the same error with the command line client and our
> solaris server, so
> this particular 413 error probably isn't TortoiseSVN related. And
> the svn:// protocol
> works fine too. Still debugging this one...)

Best guess for that failure: your apr library on the server is not
compiled with large file support.