public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] emerge world taking excessive CPU/real time
Date: Sat, 31 Oct 2009 12:36:53 -0700	[thread overview]
Message-ID: <4AEC91D5.5010804@gentoo.org> (raw)
In-Reply-To: <deaa866a0910310713t365c5c32r4864056d210a5f77@mail.gmail.com>

Robert Bradbury wrote:
> I commonly run:
>   emerge --pretend --update --verbose --deep --newuse world
> at least once every day to provide a list of recently updated packages
> that I need to re-emerge.
> 
> I've noticed recently (in the last 1-2 weeks) that it seems to be taking
> a very long time.  The one I've got running now has on the order of 8+
> CPU minutes which seems very long.  I think this used to take <2 minutes.

Maybe it's backtracking for some reason. If that's the case, should
see some related messages about backtracking. Please file a bug at
http://bugs.gentoo.org and include --pretend --debug output for the
long-running dependency calculation.

> I've also noticed some chatter on the gentoo-dev list about including
> package dates in the portage database.
> 
> Has anyone else encountered this problem or have any ideas about the
> possible cause?  Could it be python version related?

I haven't seen any other reports like this. I doubt that the python
version is related.

> Versions are: portage-2.1.7.1 and Python 2.6.3 (r263:75183, Oct  3 2009,
> 02:52:55).
> 
> Thanks,
> Robert
> 
> 


-- 
Thanks,
Zac



  reply	other threads:[~2009-10-31 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31 14:13 [gentoo-dev] emerge world taking excessive CPU/real time Robert Bradbury
2009-10-31 19:36 ` Zac Medico [this message]
2009-11-01  0:32   ` Zac Medico

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=4AEC91D5.5010804@gentoo.org \
    --to=zmedico@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