From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Rewrite doins in python (bug 624526)
Date: Mon, 14 Aug 2017 20:49:43 +0100 [thread overview]
Message-ID: <be063406-660b-7cc6-e995-a8cb895a832f@iee.org> (raw)
In-Reply-To: <20170814073921.20837-1-zmedico@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]
On 14/08/17 08:39, Zac Medico wrote:
> From: Hidehiko Abe <hidehiko@chromium.org>
>
> doins is written in bash. However, specifically in case that
> too many files are installed, it is very slow.
> This CL rewrites the script in python for performance.
>
> BUG=chromium:712659
> TEST=time (./setup_board --forace && \
> ./build_package --withdev && \
> ./build_image --noenable_rootfs_verification test)
> ===Before===
> real 21m35.445s
> user 93m40.588s
> sys 21m31.224s
>
> ===After===
> real 17m30.106s
> user 94m1.812s
> sys 20m13.468s
>
I know I'm gonna get chewed out on this one, but here goes anyway ...
Surely for a package like chromium, who's build time is already in the
'hours' range anyway, surely a couple of minutes gain for the install
phase is neither here nor there?! If there were some genuine filesystem
iop gains/etc for this change, I think I'd likely support it further ..
On this basis, what do the performance differences look like on an
'average' package .. and are there any regressions in this regard?!
I take issue with the copyright assignment, as I believe the legal ..
err .. IANAL devs are campaigning for full rights to be owned and
enforced by Gentoo Inc LLC in the US .. even if they have no idea what
that means or does .. :]
MJE
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-08-14 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 7:39 [gentoo-portage-dev] [PATCH] Rewrite doins in python (bug 624526) Zac Medico
2017-08-14 19:49 ` M. J. Everitt [this message]
2017-08-14 20:31 ` Zac Medico
2017-08-22 14:21 ` Brian Dolbec
2017-08-23 14:51 ` Michał Górny
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=be063406-660b-7cc6-e995-a8cb895a832f@iee.org \
--to=m.j.everitt@iee.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