Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Sorcery and the Broken Cache

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Sorcery and the Broken Cache
  • Date: Fri, 15 Jul 2005 17:56:30 -0500

On Jul 16, Karsten Behrmann [BearPerson AT gmx.net] wrote:
> On Fri, 15 Jul 2005 14:45:29 -0700 Andrew wrote:
>
> > scribe with rsync in my project branch doesnt take very long, on the
> > order of 30 seconds or less to do an empty update...

An empty rsync update of test grimoire here takes over 2 minutes.
Interestingly, doing a full tarball download takes only 1 minute. I would
prefer to use rsync to be nice to the bandwidth, but when it takes 10-15
minutes to do a 'sorcery update && scribe update', it's a bit silly. Of
course I also don't want to be rude to bandwidth and do a regular http
update each time, hence suggesting the md5 check. Applied to either method
it would take the time down to nearly nothing when nothing has changed.
Call that suggesting unnecessary bloat if you must.

> Actually, try "uncommenting" my rsync progress bar.
> running some bash code every line is expensive, not too noticeable
> (I hope) on working syncs, but I think it could almost be the ham of
> those 30 seconds on dry runs...
>
> Oh yeah, that's my code... Didn't quite know where to and where not to use
> bash in those days... maybe some small awk script just outputting
> "<kill line>xx%" continuously would do better. And watch out if you're
> outputting progress to a file...
> maybe rsync --progress, despite its slightly ugly looks, could be the
> best solution for us

Maybe this is the real issue.

Attachment: pgpT3BMttNCJk.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page