Hi * - repost because it was not answered for >two weeks. If the question is too stupid to deserve an answer, please tell me at least that...
On Thu, Aug 21, 2008 at 12:51 AM, Christian Lohmaier <[EMAIL PROTECTED]> wrote: > Hi *, > > I was looking for new ways to handle the sourcecode on > tinderboxes/buildbots and thought since the svn will start over from > scratch (more or less), without much historical ballast, I thought > about mirroring the svn repository and do local checkouts. > (currenlty I keep copies of milestone checkouts locally). > > I intended to check how much diskspace that would need and then decide > on how to proceed. But svnsync is nearly unusable, since the transfer > rates are so slow. > > While I get > 500KiB/s with a svn co of the trunk, the svn sync runs at > <10KiB/s > > Is there an artificial limit imposed on svnsync? > > And maybe you have another idea of handling the sourcecode locally? I > try to avoid wasting bandwidth by downloading hundreds of MB for each > build tinderbox does. > Downloading a 6-7GB repository once is fine, downloading 370MB (size > of a tar.gz of the full sources) 200 times is not... > Also downloading those 6/7GB with 3KiB/s is not OK either. > > Besides the bandwidth itself, time needed for a checkout is also a > point why I'd prefer a local copy. > > I thought about a svn mirror because I think that instead of having > full copies of the files, svn works with the differences between > revisions, so I might even save some bits of data storage, at least > for a year or so (currently, the tinderboxes have around of 10 to 20 > GB of sourcetarballs lying around). > > ciao > Christian > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
