public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Zeindl <fabian.zeindl@gmx.at>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Proposal for an alternative portage tree sync method
Date: Wed, 23 Mar 2005 12:15:25 +0100	[thread overview]
Message-ID: <42414FCD.10106@gmx.at> (raw)
In-Reply-To: <200503222358.50671.gentoo-dev@wizy.org>

[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]

There was a proposal some times ago about replacing the current portage
tree with a database which contains packagenames, dependencies etc. but
no ebuilds with installation instructions.
The ebuild will be downloaded by emerge <package>.

I think this would be a more interesting way of accelerating portage and
reduce load from the rsync-mirrors...

lg
fabian

Ricardo Correia wrote:
> On Tuesday 22 March 2005 12:45, Daniel Drake wrote:
>
>>So on every sync, you have to download the entire 260mb ISO file?
>>
>>I don't think our mirrors would be very happy about that.
>>
>>Daniel
>>--
>>gentoo-dev@gentoo.org mailing list
>
>
> You don't seem to have understanded how zsync works.
>
> Suppose that I, as a user, already have yesterday's portage ISO file.
> And suppose that today, there's about 30 new or updated ebuilds.
> Also suppose that those ebuilds amount to something like 500 KB.
>
> In those conditions, if I update my ISO file today using zsync, I would only
> have to download the zsync file (which would be about 700 KB) and the
> necessary *compressed* ranges of the (compressed) ISO file available on the
> mirror. This would be *less* than 500 KB, because of the compression.
>
> This works because the .zsync file contains a mapping of the uncompressed data
> to the compressed data.
>
> Notice that even if the user doesn't have the ISO file yet, he would only have
> to download about 27 MB.
>
> Personally, I estimate that updates could be faster than a rsync, if not only
> because of the whole disk thrashing. But only through experimentation we
> would be able to measure the difference.
>
> Also notice that zsync still has lots of room for improvements, so I wouldn't
> be surprised to see it beat rsync in terms of time of an update.
>
> I think it's worthwhile to setup an experimental mirror, it sure seems much
> better than doing emerge-webrsync..
> --
> gentoo-dev@gentoo.org mailing list
>
>


--
Musik kann nicht illegal sein: www.fairsharing.de

I prefer signed/encrypted Mail:
Fingerprint: CFE8 38A7 0BC4 3CB0 E454  FA8D 04F9 B3B6 E02D 25BA

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-03-23 10:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22  7:15 [gentoo-dev] Proposal for an alternative portage tree sync method Ricardo Correia
2005-03-22 12:45 ` Daniel Drake
2005-03-22 12:59   ` Paul Waring
2005-03-22 13:22   ` Francesco Riosa
2005-03-22 15:03     ` Simon Stelling
2005-03-22 14:39       ` Stroller
2005-03-22 23:58       ` Ricardo Correia
2005-03-22 23:58   ` Ricardo Correia
2005-03-23 11:15     ` Fabian Zeindl [this message]
2005-03-23 18:03       ` Marius Mauch
2005-03-22 13:55 ` Patrick Lauer
2005-03-22 15:19   ` Simon Stelling
2005-03-22 23:58   ` Ricardo Correia
2005-03-23 22:15     ` Nick Rout
2005-03-23 22:49       ` Ricardo Correia
2005-03-24 14:11 ` Karl Trygve Kalleberg
2005-03-25  7:57   ` Brian Harring
2005-03-26 12:45     ` Karl Trygve Kalleberg
2005-03-27 19:03       ` Brian Harring
2005-03-28 13:04 ` Petteri Räty

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=42414FCD.10106@gmx.at \
    --to=fabian.zeindl@gmx.at \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.org \
    /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