From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Remove "dev"-status of mips profiles
Date: Thu, 11 Feb 2010 10:41:41 -0800 [thread overview]
Message-ID: <20100211184141.GB20770@hrair> (raw)
In-Reply-To: <20100211160404.TAb70b3.tv@veller.net>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
On Thu, Feb 11, 2010 at 04:54:38PM +0100, Torsten Veller wrote:
> Can we please move the mips profiles from "dev" to "exp" in
> profiles/profiles.desc?
>
>
> The ~150 mips development profiles increase the time for a
> `repoman -d full` run in dev-perl/ from three to five minutes. That is
> an increase of roughly 66 percent.
> repoman further prints more than 2000 lines of output for two keywording
> problems.
Quick pcheck visibility scan of the full tree, stats follow:
mips profiles still enabled:
* 116191 seperate dependency issues, 1 line per profile/dependency
issue
* roughly 2m39s run time
mips profiles disabled (leaving mips-irix however)
* 9550 seperate dependency issues, 1 line per profile/dependency issue
* roughly 1m54s run time.
So... mips accounts for about 30% of the pcheck runtime, and *92%* of
known visibility issues. As for the runtime difference between
pcheck/repoman, pcheck has some tricks internally to reduce the # of
profiles it has to scan down to just the unique USE/mask set- I'd
expect the mips impact to be far larger w/out that trick in place.
At the very least if it's going to be kept around, experimental or
not, the number of profiles in use there *really* needs reduction-
mips has roughly 117 profiles listed in profiles.desc out of 217-
literally ~54% of all dev/stable/experimental profiles.
Either way, stats to chew on.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-02-11 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 15:54 [gentoo-dev] Remove "dev"-status of mips profiles Torsten Veller
2010-02-11 16:06 ` [gentoo-dev] " Christian Faulhammer
2010-02-11 18:41 ` Brian Harring [this message]
2010-02-11 18:56 ` [gentoo-dev] " Jeremy Olexa
2010-02-11 19:08 ` Brian Harring
2010-02-11 19:16 ` Brian Harring
2010-02-11 19:21 ` Samuli Suominen
2010-02-11 21:12 ` [gentoo-dev] " Christian Faulhammer
2010-02-11 21:22 ` Brian Harring
2010-02-25 10:30 ` Torsten Veller
2010-02-25 15:14 ` Mark Loeser
2010-02-25 15:24 ` Samuli Suominen
2010-02-25 19:29 ` Robin H. Johnson
2010-02-25 23:57 ` Ryan Hill
2010-02-26 6:57 ` Torsten Veller
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=20100211184141.GB20770@hrair \
--to=ferringb@gmail.com \
--cc=gentoo-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