From: Dale <dalek@exceedtech.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge starts slowly
Date: Thu, 15 Dec 2005 03:59:51 -0600 [thread overview]
Message-ID: <43A13E97.3070401@exceedtech.net> (raw)
In-Reply-To: <20051215094922.24263df8@hactar.digimed.co.uk>
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.
>
>
>
>
Just so you won't feel alone, same here. I mostly do this on #1 below
in my sig. Don't get me started on #4. LOL It's slow at everything. :(
I think the new portage is supposed to be better. That is what I have
read anyway. I dunno for sure. To chicken to keyword it. LOL
Dale
:-)
--
To err is human, I'm most certainly human.
I have four rigs:
1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives.
2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB drive.
4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive.
All run Gentoo, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-15 10:11 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 [this message]
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
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=43A13E97.3070401@exceedtech.net \
--to=dalek@exceedtech.net \
--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