Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Fredrik Gustafsson" <fredrik.gustafsson@axis.com>
To: Ross Burton <ross@burtonini.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	tools-cfpbuild-internal <tools-cfpbuild-internal@axis.com>
Subject: Re: [OE-core] Add package managers as a plugin
Date: Tue, 30 Jun 2020 19:01:23 +0000	[thread overview]
Message-ID: <1593543683295.70380@axis.com> (raw)
In-Reply-To: <CAAnfSTuK-ucvmFTK9+oexvPyaXgTg4Tn3nhKSMwjhRxe=NUXrw@mail.gmail.com>

Hi Ross,
those 5 seconds will increase to minutes for my use case and we build a lot
hence I hope this will save us a lot of computer power and engineering time.
For example I've sent numbers on building a bigger image (core-image-sato-sdk-ptest)
to Alex and Alex:
out.apk.1: 1:13.35
out.apk.2: 1:13.51
out.apk.3: 1:13.23
out.apk.4: 1:14.07
out.apk.5: 1:13.00
out.deb.1: 3:49.37
out.deb.2: 3:50.77
out.deb.3: 3:51.39
out.deb.4: 3:53.40
out.deb.5: 3:53.99
out.ipk.1: 2:38.99
out.ipk.2: 2:39.07
out.ipk.3: 2:35.34
out.ipk.4: 2:36.15
out.ipk.5: 2:34.55
out.rpm.1: 1:58.61
out.rpm.2: 1:59.42
out.rpm.3: 1:59.70
out.rpm.4: 1:58.96
out.rpm.5: 1:58.11

Also consider that if we've a target without python with limited space, rpm is out
of the question. So the real comparison would be between ipk and apk. Let's
say we can save 80 seconds in each build. Now multiply that with the number of
builds, and we do a lot (I guess we might approach 100 000 builds/week in the
next year). Then this will save 92.5 days build time each week.

That's why I'm passionated about this.

/Fredrik
________________________________________
From: Ross Burton <ross@burtonini.com>
Sent: Friday, June 26, 2020 12:52 PM
To: Fredrik Gustafsson
Cc: OE-core; tools-cfpbuild-internal; Hugo Cedervall
Subject: Re: [OE-core] Add package managers as a plugin

On Thu, 25 Jun 2020 at 11:14, Fredrik Gustafsson
<fredrik.gustafsson@axis.com> wrote:
> Poky today has three different package managers, the well-known formats deb
> and rpm is supported as well as ipkg that is good for embedded devices.
>
> When building and having a good cache hit, a significant amount of time is
> spent in the phase of generating a rootfs, which is really about the
> performance of the package manager. ipkg is way slower than deb or rpm. To
> save build time and also get a package manager that is suitanle for use on
> targets where flash memory is a concern, support for apk is suggested.
>
> However, it might or might not be what's wanted for Poky since it increases
> the test matrix. Therefore this patch series refactors the package
> management code so that it's possible to add more package managers in other
> own layer. I will send another patch serie that will add apk.

As to the code review I mostly second what Paul said.

However, obviously you actually have strong feelings on this as the
series represents a fair amount of work.  What are the compelling
reasons to use apk?  Five seconds on core-image-minimal doesn't really
sell it to me, I don't think anyone ever claimed that opkg has been
performance optimised, dpkg isn't really used that much: maybe we
should re-evaluate what package managers are supported if apk has
feature parity but is significantly faster or has other advantages.

Ross

  parent reply	other threads:[~2020-06-30 19:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 10:13 Add package managers as a plugin Fredrik Gustafsson
2020-06-25 10:24 ` [OE-core] " Alexander Kanavin
2020-06-30 15:04   ` Fredrik Gustafsson
2020-06-30 15:43     ` Alexander Kanavin
2020-06-30 18:46       ` Fredrik Gustafsson
2020-06-26 10:52 ` Ross Burton
2020-06-27  4:59   ` Tim Orling
2020-06-30 15:36   ` Khem Raj
2020-06-30 19:01   ` Fredrik Gustafsson [this message]
2020-06-30 21:54     ` Martin Jansa
2020-06-30 22:12       ` Fredrik Gustafsson
2020-07-01 19:12         ` Alejandro del Castillo
2020-06-30 23:15       ` Andre McCurdy
2020-07-01  0:16         ` Martin Jansa
  -- strict thread matches above, loose matches on Subject: below --
2020-07-02 19:29 Fredrik Gustafsson
2020-07-02 20:28 ` [OE-core] " Paul Barker
2020-07-03 11:45   ` Fredrik Gustafsson
2020-06-25 10:21 Fredrik Gustafsson
2020-06-25 10:40 ` [OE-core] " Paul Barker
2020-06-30 18:39   ` Fredrik Gustafsson
2020-06-23 11:13 Fredrik Gustafsson
2020-06-23 18:50 ` [OE-core] " Denys Dmytriyenko
2020-06-30 15:15   ` Fredrik Gustafsson
2020-06-24 15:18 ` Alex Stewart
2020-06-30 18:38   ` Fredrik Gustafsson
2020-06-30 20:22     ` Alex Stewart

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=1593543683295.70380@axis.com \
    --to=fredrik.gustafsson@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.com \
    --cc=tools-cfpbuild-internal@axis.com \
    /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