public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Re: portage-ng roadmap?
Date: Mon, 12 Jul 2004 05:44:33 -0500	[thread overview]
Message-ID: <1089629073.32038.8.camel@6-allhosts> (raw)
In-Reply-To: <20040712111714.1dfc2653@localhost>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

On Mon, 2004-07-12 at 04:17, Michael Kohl wrote:
> On Mon, 12 Jul 2004 11:08:16 +0200
> Philippe Lafoucrière <lafou@wanadoo.fr> wrote:
> 
> > I'd like to work on the cache part, since I'm getting sic of "emerge
> > rsync".
> 
> 2.0.51 is changing the cache format. I don't know yet if this makes
> "emerge sync" faster, but if you're eager to try it out you can unmask
> it in your /etc/portage/package.unmask.
The change is due to the addition of provide's to the cache; that
doesn't affect speed, although .51 is a bit faster since a couple of
issues w/ the cache handling code have been corrected.

Main one being the addition of __cache(Array|Key) to portage_db_template
storing the last 3 keys pulled for that category, correcting an issue w/
aux_get where it went to disk *way* more then was needed.  At some point
I'd think the __cache(Array|Key) addition should be moved up above the
portage_db layer, since w/ right now it makes addition of a memcached
based cache semi-tricky/ugly.
~brian

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-12 10:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  8:44 [gentoo-portage-dev] portage-ng roadmap? Adrian Gschwend
2004-06-28 14:08 ` Marius Mauch
2004-06-28 22:55   ` Roman Gaufman
2004-06-29  7:52   ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-29 18:44     ` Hasan Khalil
2004-06-29 21:15       ` George Shapovalov
2004-06-30  9:03         ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30  9:07           ` John Nilsson
2004-06-30  9:24             ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30 20:07           ` [gentoo-portage-dev] " Paul de Vrieze
2004-06-30 21:41             ` Brian Harring
2004-06-30 22:23               ` Nathaniel McCallum
2004-07-01  9:25                 ` Paul de Vrieze
2004-07-12  9:08             ` Philippe Lafoucrière
2004-07-12  9:17               ` Michael Kohl
2004-07-12 10:44                 ` Brian Harring [this message]
2004-07-15 13:30               ` Paul de Vrieze
2004-07-16  7:14                 ` Philippe Lafoucrière
2004-07-16  8:10                   ` Paul de Vrieze
2004-07-16  8:49                     ` Philippe Lafoucrière
2004-07-04 21:35           ` Pieter Van den Abeele
2004-07-05 11:05             ` [gentoo-portage-dev] " Adrian Gschwend
2004-07-05 21:24               ` Pieter Van den Abeele
2004-07-07 20:54             ` [gentoo-portage-dev] " gentoo
2004-07-07 19:49               ` [gentoo-portage-dev] unsubscribing (was: Re: portage-ng roadmap?) Andrew Gaffney
2004-06-30  9:03       ` [gentoo-portage-dev] Re: Re: portage-ng roadmap? Adrian Gschwend
2004-06-30 13:06         ` Hasan Khalil
2004-07-04 21:45   ` [gentoo-portage-dev] " Pieter Van den Abeele
  -- strict thread matches above, loose matches on Subject: below --
2004-07-16 10:04 [gentoo-portage-dev] Re: " Paul de Vrieze

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=1089629073.32038.8.camel@6-allhosts \
    --to=ferringb@gentoo.org \
    --cc=gentoo-portage-dev@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