On Wed, Jun 6, 2012 at 5:13 AM, Mat Booth <mat.bo...@wandisco.com> wrote:
> On 31 May 2012 17:14, Ulrich Eckhardt <ulrich.eckha...@dominolaser.com>wrote: > >> Am 31.05.2012 17:45, schrieb David Weintraub: >> [SVN long distance performance problems] >> > * Is there another solution? What about svnsync? >> >> svnsync will greatly speed up the update, checkout and log access. You >> can configure it to automatically push changes to connected repositories >> on commit, so remote people don't have to do anything. svnsync doesn't >> change commit times though, because committing still goes (indirectly >> via a proxy) to the main repository, which solves any distributed sync >> issues. >> >> > However, I still need the multisync features. >> >> What are those? svnsync doesn't add any features, it just improves >> performance in the above cases by providing a more local cache. Well, it >> adds distributed, redundant storage of data, but that's all. >> >> > WANdisco MultiSite differs from svnsync by offering a multi-master node > setup where users can use their closest node geographically in order to > improve both check out and commit speed. > I'm also impressed with your company's attention to fail-over behavior, so that the failure of the "master" node does not stop updates cold, and so that access configurations and pre/post commit operations don't have to be mirrored with some handwritten, out of band operation. Complete solutions are invaluable for sites that don't have a skilled local admin who has the time and skill to build those up from scratch reliably.
