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

RE: Recommendations for Caching Proxy or other method for Performance Issues with disparate Development Teams

From: Kenneth Wood <kenneth.wood_at_e2open.com>
Date: 2007-01-20 00:04:06 CET

I've done some experimenting with this approach, but haven't had much
time
to really work it out...
 
But...
 
What I plan to do, based on other things I've found in the web, is this:
 
a. install SVK and SVN on a server in the remote location.
b. use SVK to create a mirror of the US based SVN repository on the
remote server
c. using SVK on the remote repo, populate the mirror from the US repo
d. using SVK, create a "working branch".
e. users in remote location use svn to check out and commit to the
working branch on their server,
    i.e. the server that, from my point of view, is "remote"
f. setup some triggers or cron jobs to sync mirror with changes from US
and sync
   US with changes from remote repo.
 
That's an outline, not details, but I hope it provides you food for
thought...

-----Original Message-----
From: Danny.McKinney@sungard.com [mailto:Danny.McKinney@sungard.com]
Sent: Friday, January 19, 2007 2:10 PM
To: users@subversion.tigris.org
Subject: Recommendations for Caching Proxy or other method for
Performance Issues with disparate Development Teams

We currently have a few repository's that contain 5,000 to 7,000 files
each we have development teams in the United States and also India that
commit changes to these repository's. The performance is fine for the
US team since the server is located here in the U.S. and the reverse for
the India team. I am looking for recommendations on either the use of a
Caching proxy or some other way to increase the performance for the
India team, yet have both team access changes with the least amount of
latency.

 

Thanks

Danny McKinney

SunGard
Received on Sat Jan 20 00:06:11 2007

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