From: Justin Krejci <jus@krytosvirus.com>
To: gentoo-user@lists.gentoo.org
Cc: Neil Bothwick <neil@digimed.co.uk>
Subject: Re: [gentoo-user] emerge starts slowly
Date: Thu, 15 Dec 2005 21:13:59 -0600 [thread overview]
Message-ID: <200512152114.00079.jus@krytosvirus.com> (raw)
In-Reply-To: <19696662.1134640252587.JavaMail.root@Sniper26>
On Thursday 15 December 2005 03:49 am, Neil Bothwick wrote:
> On Thu, 15 Dec 2005 00:14:13 -0600, Justin Krejci wrote:
> > When I run "emerge -s whatever" or "emerge sync" or any emerge command
> > apparently, it usually takes about 1 second to start the command on the
> > AMD64 system whereas on the Athlon-XP system it usually takes about
> > 10-30 seconds fore the command to start.
>
> Is that just the first time you run a portage command? I see the same on
> my AMD64, it can take up to 30 seconds to run emerge --info, but only
> around a second to run it again.
>
> It's clearly something to do with loading the various Python libraries,
> classes or modules, but I haven't been able to pin down why it takes so
> long.
Yes, the second run and subsequent runs for a period of time all seem to be
fairly quick, but I thought it odd that my AMD64 system is always quick.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-16 3:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 6:14 [gentoo-user] emerge starts slowly Justin Krejci
2005-12-15 9:49 ` Neil Bothwick
2005-12-15 9:59 ` Dale
2005-12-15 12:08 ` Neil Bothwick
2005-12-15 13:24 ` Dale
2005-12-15 15:25 ` Neil Bothwick
2005-12-15 15:45 ` Richard Fish
[not found] ` <19696662.1134640252587.JavaMail.root@Sniper26>
2005-12-16 3:13 ` Justin Krejci [this message]
2005-12-18 19:19 ` Daniel Drake
[not found] ` <7696767.1134661621163.JavaMail.root@sniper5>
2005-12-16 3:34 ` Justin Krejci
2005-12-17 3:04 ` cucu ionut cristian
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=200512152114.00079.jus@krytosvirus.com \
--to=jus@krytosvirus.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=neil@digimed.co.uk \
/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