public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Diamond <diamond@hi-net.ru>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item review: SquashDelta syncing support
Date: Fri, 15 May 2015 19:15:18 +0300	[thread overview]
Message-ID: <20150515191518.1ccd2ee0@diamond.mlzone> (raw)
In-Reply-To: <CAKmKYaANsxTjD0=jNw_N0JQ8fe+8mf5=_6GqMCLGwHFiTBxzFw@mail.gmail.com>

On Fri, 15 May 2015 08:23:27 -0700
Dirkjan Ochtman <djc@gentoo.org> wrote:

> On Fri, May 15, 2015 at 7:51 AM, Michał Górny <mgorny@gentoo.org>
> wrote:
> > Starting with Portage 2.2.19, a new SquashDelta syncing method has
> > been introduced. It is meant to provide lightweight and efficient
> > solution for stable systems. The whole repository is contained
> > within a single pre-generated SquashFS image file. The daily
> > snapshot of the repository is first fetched from the mirrors, and
> > afterwards updated in-place using deltas (without repacking).
> 
> This sounds nice, but the news item currently leaves me wondering what
> sort of improvements I should expect. It says the new method is
> "lightweight and efficient", but it would be nice to quantify this a
> little bit, or add a link to a page with more details. I think the
> default sync method in the handbook up to now has always been rsync? A
> comparison (both in terms of upside and in terms of downside) would be
> nice. Also, whether we want to make this the new default at some
> point, and if so, when.
> 
> Cheers,
> 
> Dirkjan
> 
> 

I've read the pdf article of Michał Górny and from my expirience with
emerge-delta-webrsync and app-portage/getdelta in the past this good old
new feature looks mostly useful for bad Internet connections (too slow
or too expensive ones) and looks mostly useless for syncing
relative to rsync method from local mirror like I use
http://mirror.yandex.ru/gentoo-distfiles/
 from my local region.
eix-sync gave me the following statistics (before introducing new
portage sync with repos.conf wich has stopped upgrade in the middle atm
because >=app-portage/layman-2.3.0 haven't been stabilised yet):
 * Time statistics:
    19 seconds for syncing
    17 seconds for eix-update
     1 seconds for eix-diff
    51 seconds total
or this one the other day:
* Time statistics:
    37 seconds for syncing
    11 seconds for eix-update
     1 seconds for eix-diff
    67 seconds total
So it takes usually 15-40 seconds for syncing using usual rsync method.
This deltas have their own drawbacks like "delta is under generation,
please wait half an hour or even more" or "your state is not the same
what was while generating delta on the host and lets do additional work
with more deltas". ))

Although, nice try with experimenting and trying to improve sync
mechanism. )


  reply	other threads:[~2015-05-15 16:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 14:51 [gentoo-dev] News item review: SquashDelta syncing support Michał Górny
2015-05-15 15:23 ` Dirkjan Ochtman
2015-05-15 16:15   ` Diamond [this message]
2015-05-15 18:32     ` Ian Stakenvicius
2015-05-15 19:33       ` Rich Freeman
2015-05-15 19:38         ` Ian Stakenvicius
2015-05-18  5:48         ` [gentoo-dev] " Martin Vaeth
2015-05-18  6:10           ` Brian Dolbec
2015-05-19  6:36             ` Martin Vaeth
2015-05-16 21:59   ` [gentoo-dev] " Michał Górny
2015-05-16 14:59 ` Michael Orlitzky
2015-05-16 18:38   ` Alexis Ballier
2015-05-16 19:18     ` Pacho Ramos
2015-05-16 19:23       ` Michael Orlitzky
2015-05-16 20:34         ` Brian Dolbec
2015-05-16 22:01         ` Michał Górny
2015-05-17  0:38           ` Michael Orlitzky
2015-05-17  3:47             ` Michał Górny
2015-05-17  8:52               ` [gentoo-dev] " Duncan
2015-05-17 18:52               ` [gentoo-dev] " Dale
2015-05-17 19:41               ` Michael Orlitzky
2015-05-20  7:56               ` Marc Schiffbauer
2015-05-16 22:00   ` Michał Górny
2015-05-17  0:45     ` Michael Orlitzky
2015-05-17  8:41       ` [gentoo-dev] " Duncan
2015-05-17 13:51     ` [gentoo-dev] " Ciaran McCreesh
2015-05-16 20:48 ` Alon Bar-Lev
2015-05-16 22:06   ` Michał Górny

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=20150515191518.1ccd2ee0@diamond.mlzone \
    --to=diamond@hi-net.ru \
    --cc=gentoo-dev@lists.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