From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team)
Date: Mon, 13 Jan 2014 08:49:17 -0800 [thread overview]
Message-ID: <CAAr7Pr-cyvnvv8useujRQBhRd-UNvTgUemyk7b+9ko=eiMBLMw@mail.gmail.com> (raw)
In-Reply-To: <20140113163859.61c3df01@gentp.lnet>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
On Mon, Jan 13, 2014 at 7:38 AM, Luis Ressel <aranea@aixah.de> wrote:
> On Mon, 13 Jan 2014 15:58:13 +0100
> Tom Wijsman <TomWij@gentoo.org> wrote:
>
> > On Mon, 13 Jan 2014 10:31:56 +0100
> > Fabio Erculiani <lxnay@gentoo.org> wrote:
> >
> > > Portage can still take *minutes* to calculate the merge queue of a
> > > pkg with all its deps satisfied.
> >
> > Half a minute if you disable backtracking which you don't need. :)
>
> Which sadly also means that some updates get skipped silently. (Those
> which would trigger rebuilds of other packages because of sub-slot
> deps, had that case yesterday).
>
> > > Ironically, launching the same emerge command twice, will take more
> > > or less the same time.
> >
> > Determinism results in more or less the same time, that's correct;
> > proper benchmarks would show you a similar result.
>
> I guess he means that the (according to the file sizes) extensive
> caching doesn't seem to be of much use.
>
The caching may not be of use, depending on your configuration. (For
example, if you use a gentoo-x86 checkout as your main repo, you will
probably want to run generate cache entries whenever you cvs up.) It is
there to cache ebuild metadata, because if your depgraph has a few thousand
nodes, having to spawn bash to generate the metadata for every node is very
expensive. That being said, for most users that use rsync, the metadata is
pre-generated. As long as they are not changing the cache indicators (not
sure if this is mtime or md5sum these days) they should be seeing a benefit.
This is not meant to imply that portage is always fast; there are plenty of
other modules (such as the aforementioned backtracking) that can take a
long time to find solutions. That is partially why you see Tomwij turning
off that feature. It is helpful for users cause it can automatically find
solutions for users that are otherwise unsolvable (and thus avoids the user
having to find a solution to the depgraph manually.)
-A
>
> --
> Luis Ressel <aranea@aixah.de>
> GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD
>
[-- Attachment #2: Type: text/html, Size: 2954 bytes --]
next prev parent reply other threads:[~2014-01-13 16:49 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 5:33 [gentoo-dev] Portage team, Zac's development break and stepping down as lead Brian Dolbec
2014-01-06 7:53 ` Dirkjan Ochtman
2014-01-06 8:27 ` Brian Dolbec
2014-01-13 3:07 ` Brian Dolbec
2014-01-13 5:05 ` Brian Dolbec
2014-01-13 8:39 ` C. Bergström
2014-01-13 8:43 ` Alexander Berntsen
2014-01-13 9:15 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) "C. Bergström"
2014-01-13 9:31 ` Fabio Erculiani
2014-01-13 9:38 ` "C. Bergström"
2014-01-13 14:58 ` Tom Wijsman
2014-01-13 15:38 ` Luis Ressel
2014-01-13 15:46 ` Tom Wijsman
2014-01-13 17:03 ` Luis Ressel
2014-01-13 18:07 ` Tom Wijsman
2014-01-13 18:05 ` Ciaran McCreesh
2014-01-13 18:19 ` Tom Wijsman
2014-01-13 16:49 ` Alec Warner [this message]
2014-01-13 17:10 ` Fabio Erculiani
2014-01-13 18:16 ` Tom Wijsman
2014-01-13 18:21 ` Ciaran McCreesh
2014-01-13 18:32 ` Tom Wijsman
2014-01-13 23:22 ` Patrick Lauer
2014-01-13 23:49 ` Tom Wijsman
2014-01-13 11:02 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Steven J. Long
2014-01-13 12:28 ` Alexander Berntsen
2014-01-13 13:06 ` Andreas K. Huettel
2014-01-13 13:50 ` Ulrich Mueller
2014-01-13 15:28 ` Tom Wijsman
2014-01-13 17:51 ` [gentoo-dev] " Ulrich Mueller
2014-01-14 7:41 ` [gentoo-dev] pkgcore EAPI-6 (Was: OT: pkgcore bikeshed) Steven J. Long
2014-01-13 15:21 ` [gentoo-dev] Re: [OT] pkgcore bikeshed Tom Wijsman
2014-01-13 20:29 ` Donnie Berkholz
2014-01-13 14:46 ` [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) Tom Wijsman
2014-01-13 14:56 ` Ian Stakenvicius
2014-01-13 15:31 ` Tom Wijsman
2014-01-13 18:01 ` Brian Dolbec
2014-01-13 18:07 ` Ciaran McCreesh
2014-01-13 18:27 ` Tom Wijsman
2014-01-13 18:37 ` Ciaran McCreesh
2014-01-14 7:56 ` [gentoo-dev] " Steven J. Long
2014-01-13 14:53 ` [gentoo-dev] " Tom Wijsman
2014-01-19 8:25 ` Mike Frysinger
2014-01-13 17:37 ` Greg KH
2014-01-13 17:42 ` "C. Bergström"
2014-01-13 17:56 ` Greg KH
2014-01-13 8:59 ` [gentoo-dev] Portage team, Zac's development break and stepping down as lead Dirkjan Ochtman
2014-01-13 14:42 ` Tom Wijsman
2014-01-13 14:46 ` Peter Stuge
2014-01-13 15:38 ` Tom Wijsman
2014-01-13 16:41 ` Alec Warner
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='CAAr7Pr-cyvnvv8useujRQBhRd-UNvTgUemyk7b+9ko=eiMBLMw@mail.gmail.com' \
--to=antarus@gentoo.org \
--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