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
