public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin Krejci <jus@krytosvirus.com>
To: gentoo-user@lists.gentoo.org
Cc: Richard Fish <bigfish@asmallpond.org>
Subject: Re: [gentoo-user] emerge starts slowly
Date: Thu, 15 Dec 2005 21:34:52 -0600	[thread overview]
Message-ID: <200512152134.52711.jus@krytosvirus.com> (raw)
In-Reply-To: <7696767.1134661621163.JavaMail.root@sniper5>

On Thursday 15 December 2005 09:45 am, Richard Fish wrote:
> On 12/14/05, Justin Krejci <jus@krytosvirus.com> 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. What I mean by that is for example
>
> You can try something like:
>
> strace -tt -f -o /tmp/strace.out emerge -s tcpdump
>
> Then look at /tmp/strace.out and see what kind of system call is being
> made that is taking so long to complete.
>
> -Richard


Well I ran it once then ran it again to a different output file and the two 
files are the same length and doing a cursory glance thru the files they both 
seem fairly similar. When I have some time, ill check the files more closesly 
in particular the timestamps.

Thanks for the idea.
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-12-16  3:40 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
2005-12-18 19:19     ` Daniel Drake
     [not found] ` <7696767.1134661621163.JavaMail.root@sniper5>
2005-12-16  3:34   ` Justin Krejci [this message]
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=200512152134.52711.jus@krytosvirus.com \
    --to=jus@krytosvirus.com \
    --cc=bigfish@asmallpond.org \
    --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