public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Portage performance dropped considerably
Date: Sun, 26 Jan 2014 19:42:56 +0200	[thread overview]
Message-ID: <52E54920.5010207@gmail.com> (raw)
In-Reply-To: <20140126162426.7a6d1f30@falcon.eroen.eu>

On 26/01/2014 17:24, eroen wrote:
> On Sun, 26 Jan 2014 16:35:43 +0200, Nikos Chantziaras
> <realnc@gmail.com> wrote:
>> Anyone else noticed this yet? Some portage update seems to have made 
>> "emerge -uDN @world" perform about 10 times slower than before. It
>> used to take seconds, now it takes about 4 minutes only to tell me
>> that there's nothing to update. And it does that every time, even
>> directly in succession and with the caches warm.
>>
>> Is it just me?
> 
> You don't say when your baseline was, but the complexity of resolving
> the package tree has increased quite a bit over the last year due to
> new features like automatic rebuilds of consumers after library updates.
> 
> Another somewhat common cause of sudden slowdowns is how portage
> resolves conflicts (like packageA requiring an old version of libraryB),
> which is rather time-consuming. You can try adding --backtrack=0 to the
> emerge command to make it stop and print an error message when
> encountering a conflict rather than look for a solution. Then you can
> 'help' out by manually resolving any conflicts by adding package
> versions to /etc/portage/package.mask . Preferably try this *after*
> running an update, so your system is up-to-date against your local
> version of the gentoo tree, otherwise "normal" simple-to-resolve
> conflicts might cause confusion. ;-)
> 

I've been noticing these slowdowns for a few months now too. I'm
somewhat conflicted in my head about them, as unresolved blockers is now
something that happens very rarely. How often did we do this in the past:

emerge -avuND world
  stare at output trying to figure out wtf?
emerge -C <some problem package>
emerge -avuND world
  emerge problem package back if world update didn't already do it

That used to happen A LOT, and it took much longer than 4 minutes.
Nowadays it happens seldom but the resolution does take 4 minutes.

So I dunno, it's annoying to have to wait, but it also prevents a lot of
wasted time by doing what software can do so well - detecting dependency
issues.



-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2014-01-26 17:43 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 14:35 [gentoo-user] Portage performance dropped considerably Nikos Chantziaras
2014-01-26 14:44 ` hasufell
2014-01-26 14:50 ` [gentoo-user] " Remy Blank
2014-01-26 15:24 ` eroen
2014-01-26 17:42   ` Alan McKinnon [this message]
2014-01-26 18:04     ` hasufell
2014-01-26 18:30       ` Alan McKinnon
2014-01-26 18:41         ` hasufell
2014-01-26 19:22           ` Alan McKinnon
2014-01-26 20:44             ` ny6p01
2014-01-27  5:03               ` Alan McKinnon
2014-01-27  9:27               ` Neil Bothwick
2014-01-26 23:26           ` William Hubbs
2014-01-26 23:36             ` Andreas K. Huettel
2014-01-27  0:44               ` Andreas K. Huettel
2014-01-27 11:44             ` hasufell
2014-01-28  1:34               ` Martin Vaeth
2014-01-28  3:19                 ` hasufell
2014-01-28 17:45                   ` Martin Vaeth
2014-01-28 18:07                     ` hasufell
2014-01-29 14:24                       ` Kerin Millar
2014-01-28  0:41             ` Walter Dnes
2014-01-28  1:42               ` Martin Vaeth
2014-01-28  4:02                 ` Walter Dnes
2014-01-31 19:03         ` Andrew Savchenko
2014-01-31 19:13           ` Mick
2014-01-31 21:18             ` Andrew Savchenko
2014-01-31 22:12               ` Alan McKinnon
2014-02-02  9:40                 ` Andrew Savchenko
2014-02-03 10:55                   ` Martin Vaeth
2014-02-03 11:57                     ` Greg Turner
2014-02-03 13:17                       ` Martin Vaeth
2014-01-26 19:29       ` Volker Armin Hemmann
2014-01-26 19:45         ` Alan McKinnon
2014-01-26 20:10           ` Volker Armin Hemmann
2014-01-27  9:30         ` Neil Bothwick
2014-01-27 11:59       ` Tanstaafl
2014-01-27 13:06         ` Alan McKinnon
2014-01-27 13:57           ` hasufell
2014-01-27 21:48             ` Neil Bothwick
2014-01-27 21:54               ` hasufell
2014-01-27 22:57                 ` Neil Bothwick
2014-01-27 23:35                   ` hasufell
2014-01-28  1:35                     ` Neil Bothwick
2014-02-03 14:04                   ` Pandu Poluan
2014-02-03 14:16                     ` Alan McKinnon
2014-02-03 16:38                       ` Pandu Poluan
2014-02-04  5:12                         ` Martin Vaeth
2014-01-28  1:50           ` Martin Vaeth
2014-01-30  3:50           ` hasufell
2014-01-30 18:15             ` [gentoo-user] " Stroller
2014-01-31 20:08               ` hasufell
2014-01-26 19:28     ` [gentoo-user] " Volker Armin Hemmann
2014-01-26 19:55       ` Alan McKinnon
2014-01-27 12:06         ` Helmut Jarausch
2014-01-27 21:56           ` Stefan G. Weichinger
2014-01-26 15:53 ` [gentoo-user] " Mariusz Ceier
2014-01-31 17:23   ` Andrew Savchenko
2014-01-26 16:06 ` Florian Philipp
2014-01-26 16:15   ` hasufell
2014-01-26 17:52     ` Florian Philipp
2014-01-26 18:16 ` covici
2014-03-07 19:36 ` Tom Wijsman
  -- strict thread matches above, loose matches on Subject: below --
2014-01-26 15:09 Greg Turner
2014-01-26 15:32 ` [gentoo-user] " eroen

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=52E54920.5010207@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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