From: Alec Warner <antarus@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Add repoman check to warn if src_prepare/src_configure are used in EAPI 0/1
Date: Sun, 19 Jan 2014 22:02:31 -0800 [thread overview]
Message-ID: <CAAr7Pr_44-04-yZTxxjsoVPWGGyQa=1G+mWNmJi6WzoLXdTQHA@mail.gmail.com> (raw)
In-Reply-To: <201401200047.29971.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Sun, Jan 19, 2014 at 9:47 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday 19 January 2014 11:59:36 Mike Gilbert wrote:
> > On Sun, Jan 19, 2014 at 4:44 AM, Mike Frysinger <vapier@gentoo.org>
> wrote:
> > > Chromium OS for a long time was restricted to EAPI 4 for two reasons --
> > > it had an old portage version (and upgrading to a newer one regressed
> > > performance significantly, so we held off until we could figure out
> why)
> >
> > I am curious to know more about the performance regression if you can
> > share. Is that something that got fixed, or did you disable some
> > features (like the slot-operator stuff)?
>
> we finally tracked it down (was due to new the new FEATURES=merge-sync
> option.
> when you're installing 200 to 500 binary packages (with like 32 in
> parallel),
> that can easily choke your throughput. some systems saw really excessive
> latencies (which i would guess was due to their drive taking longer to
> process
> dirty blocks). but it took us some time to figure that out as we were
> making a
> large version jump and we didn't have too much time to dedicate to
> tracking it
> down. lots o bugs to fix.
> -mike
>
Are you still doing crazy crap like disabling all of the portage locking? ;p
-A
[-- Attachment #2: Type: text/html, Size: 1910 bytes --]
next prev parent reply other threads:[~2014-01-20 6:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 16:59 [gentoo-portage-dev] [PATCH] Add repoman check to warn if src_prepare/src_configure are used in EAPI 0/1 Mike Gilbert
2014-01-20 5:47 ` Mike Frysinger
2014-01-20 6:02 ` Alec Warner [this message]
2014-01-20 6:40 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2014-01-14 0:08 creffett
2014-01-14 0:50 ` Mike Frysinger
2014-01-14 3:23 ` Tom Wijsman
2014-01-14 4:59 ` Mike Frysinger
2014-01-14 5:37 ` Brian Dolbec
2014-01-14 6:37 ` Mike Frysinger
2014-01-14 21:15 ` Tom Wijsman
2014-01-19 9:44 ` Mike Frysinger
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='CAAr7Pr_44-04-yZTxxjsoVPWGGyQa=1G+mWNmJi6WzoLXdTQHA@mail.gmail.com' \
--to=antarus@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