On Thu, 25 Oct 2007, Jack Repenning wrote:
> On Oct 25, 2007, at 6:41 AM, David Summers wrote:
>
>
>> The master is in Huntsville, AL, and the slave is in Lowell, AR, across the
>> Internet. Most of the time there is no problem at all but when the the
>> commit passes some magic number of bytes or seconds then the client freaks
>> out. The other day, I kept getting errors from the client for 1.5 hours
>> after the (big) commit until the slave and master had synced up.
>
> Does the commit part of the commit take 1.5 hours? That is, does it seem
> like this commit is big enough that "1.5 hours" is a reasonable estimate for
> how long it takes to transfer the data?
>
> We've all been kind of assuming that this 1.5 hours was the legitimate time
> needed for a post-commit svnsync to transfer the data back to the slave(s).
> But, geez, 1.5 hours? On a one time-zone US Internet connection? What are
> we committing, here, terabytes? Maybe the explanation's a bit deeper,
> somehow?
>
I believe that the original commit took approx as long as the sync, so
yes, it probably took about 1 - 1.5 hours for the commit. It was probably
on the order of 1 Gigabyte across the internet for the original commit and
I'm fairly sure it was about 1.5 hours for the svnsync back to our local
slave server from the master in Huntsville because I started watching the
network traffic between the machines while I compared the repository
versions on both machines by browsing them in my web browser.
--
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 25 14:47:07 2007