> -----Oorspronkelijk bericht-----
> Van: Hyrum K. Wright [mailto:hyrum_at_hyrumwright.org]
> Verzonden: woensdag 24 juni 2009 17:14
> Aan: John Beranek
> CC: users_at_subversion.tigris.org
> Onderwerp: Re: Speed issues with ra_neon to remote repositories
> On Jun 24, 2009, at 10:05 AM, John Beranek wrote:
> > Bob Archer wrote:
> >>> Bob Archer wrote:
> >>>>> OK, so on the surface ra_svn is clearly the solution...except
> >>>>> you can't do transparent proxying of reads/writes to a local
> >>>>> slave with ra_svn...so you're going have to get to the
> >>>>> situation of doing general read operations from the local
> >>>>> slave, either with ra_svn or ra_neon and then when you do a
> >>>>> (large) commit have to switch to
> >>> using
> >>>>> ra_svn. This will either require a deal of effort for the
> >>>>> individual engineer, or a script to perform this for them.
> >>>> My first question would be, do you "really" need the
> >>>> slave/mirrors?
> >>> We have development that is shared across sites. So, yes.
> >>> John.
> >> We do too... three sites. Yet, we only have a single repo server
> >> one site that all users access.
> > That wouldn't help though - commits from India direct to the UK
> > are still _very_ slow.
> Subversion's HTTPv2, a reduced-turnaround implementation of the DAV
> protocol will debut in Subversion 1.7. It doesn't help you *now*,
> hopefully it will have significant impact on high-latency links,
> as from India to the UK. You can read about it here:
Unfortunately, it says:
- enable pipelined PUTs [OUT-OF-SCOPE]
which may be just what the OP is after ...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-24 18:04:28 CEST