public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <3942E532.5D17574@cygnus.com> (raw)
In-Reply-To: <394223B7.A1A849E9@cygnus.com>

Jason Molenda wrote:

> ??  Rsync recognizes blocks of data.  It doesn't interpret the
> syntax of a .c file, run an SGML parser on an .html file, or try
> to parse the English sentences in a .txt file.  A block of random
> data and a block of human-readable data are little different to
> rsync.

Given two nightly snapshots there are very few differences.  Once the
tar ball has gone through gzip, however, all similarity is lost.

Its a lot more efficient to rsync the uncompressed tar-ball than it is
to down load the compressed version (well it is for me :-).

> Are you making this all up on your own - assuming that there is a
> problem - or is there some actual evidence of a problem?  I don't
> mean to be harsh, but I seem to be engaged in an intellectual
> discussion of the tone "I bet rsync is slow doing foo and we should
> change how we do things.  Someone should prove to me otherwise."

Not so much a problem of ``rsync is slow'' but rather, is there a better
way.  

One issue raised by individual testers during the gdb 5.0 release
process was the logistics of repeatedly draging down 10mb tar-balls. 
Next time around I'll have the un-compressed tar ball available.  It
occures to me that this could be scaled :-)

	enjoy,
		Andrew

WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp mirrors
Date: Sat, 10 Jun 2000 18:03:00 -0000	[thread overview]
Message-ID: <3942E532.5D17574@cygnus.com> (raw)
Message-ID: <20000610180300.e8yg4mCXS-A_nuygfwuA88FK3kiV02IVOGFGl4s_2hk@z> (raw)
In-Reply-To: <394223B7.A1A849E9@cygnus.com>

Jason Molenda wrote:

> ??  Rsync recognizes blocks of data.  It doesn't interpret the
> syntax of a .c file, run an SGML parser on an .html file, or try
> to parse the English sentences in a .txt file.  A block of random
> data and a block of human-readable data are little different to
> rsync.

Given two nightly snapshots there are very few differences.  Once the
tar ball has gone through gzip, however, all similarity is lost.

Its a lot more efficient to rsync the uncompressed tar-ball than it is
to down load the compressed version (well it is for me :-).

> Are you making this all up on your own - assuming that there is a
> problem - or is there some actual evidence of a problem?  I don't
> mean to be harsh, but I seem to be engaged in an intellectual
> discussion of the tone "I bet rsync is slow doing foo and we should
> change how we do things.  Someone should prove to me otherwise."

Not so much a problem of ``rsync is slow'' but rather, is there a better
way.  

One issue raised by individual testers during the gdb 5.0 release
process was the logistics of repeatedly draging down 10mb tar-balls. 
Next time around I'll have the un-compressed tar ball available.  It
occures to me that this could be scaled :-)

	enjoy,
		Andrew

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200006091545.LAA00938.cygnus.project.sourcemaster@envy.delorie.com>
2000-12-30  6:08 ` Jim Kingdon
2000-06-09 14:53   ` Jim Kingdon
2000-12-30  6:08   ` Andrew Cagney
2000-06-09 22:05     ` Andrew Cagney
2000-12-30  6:08     ` Jason Molenda
2000-06-10  1:02       ` Jason Molenda
2000-12-30  6:08       ` Jason Molenda
2000-06-10  1:08         ` Jason Molenda
2000-12-30  6:08       ` Andrew Cagney
2000-06-10  4:19         ` Andrew Cagney
2000-12-30  6:08         ` Andrew Cagney [this message]
2000-06-10 18:03           ` Andrew Cagney
2000-12-30  6:08           ` Jason Molenda
2000-06-10 23:55             ` Jason Molenda
2000-12-30  6:08             ` Jim Kingdon
2000-06-11  8:24               ` Jim Kingdon
2000-12-30  6:08               ` Jason Molenda
2000-06-11 15:08                 ` Jason Molenda
2000-12-30  6:08         ` Jason Molenda
2000-06-10  9:39           ` Jason Molenda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3942E532.5D17574@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=jason-swarelist@molenda.com \
    --cc=overseers@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).