public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: leio@hercules.dustbite.org
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] What happend to portage speed?
Date: Sun, 31 Aug 2003 17:16:17 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308311711090.14137-100000@hercules.dustbite.org> (raw)
In-Reply-To: <3F51EFB3.7050303@milsson.nu>

On Sun, 31 Aug 2003, John Nilsson wrote:

> No, no. The download is quick. But the calculation of deptree and that 
> kind of things that takes so much time.
> 
> Also what is this metadata directory? (Sorry for not RTFM).
> 
> -John
> 

After every rsync it rebuilds the cache... at least by default.
That's what takes the most time with an emerge sync on my 166MHz computer.
It was discussed a while ago that the cache has changed maybe by 5%, but 
it does it all again. Parses some things, writes lots of files to cache, 
etc. There were ideas how to make it quick again, but unfortunately either 
no-one has brought it to reality or into the official portage.
If that's not your speed problem, disregard this e-mail, but I believe 
this the most time demanding operation with emerge sync as of now.

Mart Raudsepp


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-31 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31  6:22 [gentoo-dev] What happend to portage speed? John Nilsson
2003-08-31  6:27 ` Jon Portnoy
2003-08-30 23:27   ` Dejan Nikic
2003-08-31 12:53     ` John Nilsson
2003-08-31 14:16       ` leio [this message]
2003-08-31 14:23         ` John Nilsson
2003-08-31 14:25           ` Riyad Kalla
2003-08-31 18:29           ` George Shapovalov
2003-08-31 18:35             ` John Nilsson
2003-09-03 15:53               ` foser

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=Pine.LNX.4.44.0308311711090.14137-100000@hercules.dustbite.org \
    --to=leio@hercules.dustbite.org \
    --cc=gentoo-dev@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