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

Re: New (1.5) feature questions -- things we need to address before a release can happen

From: Jack Repenning <jrepenning_at_collab.net>
Date: 2007-10-25 07:44:32 CEST

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?

Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 25 07:44:45 2007

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

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