From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 01/10] package: Move fixup_perms function to bb function library
Date: Wed, 04 Jan 2023 16:25:23 +0000 [thread overview]
Message-ID: <4a8cbda140f676a63cff3e13678bcd8407ef50dd.camel@linuxfoundation.org> (raw)
In-Reply-To: <173725B379431FBC.11747@lists.openembedded.org>
I'd guess people might be curious on the actual parsing/cache impacts
of this series.
To be honest I'm having trouble isolating a parsing time change for it,
which is quite sad. Someone with a slower system or limiting it to a
small set of cores might get some better results. I can see slight
reductions in the generate_dependencies function times. I was also
profiling the "bitbake -S" cache mode, better results might be obtained
without enabling that.
It does reduce the overall "bitbake -S none" cache file size by around
420k (on a 74MB file). Much more significantly, it also reduces the
do_package sigdata file from 224k to 159k uncompressed or 54k -> 36k
compressed (which the files are).
Whilst those improvements don't sound much, this is a significant
reduction in the amount of data bitbake is chucking around pipes
internally and the reduction in size of the sigdata will mount up over
many recipes/tasks in an sstate share.
I do think we can end up with cleaner more understandable/maintainable
code if we do this correctly so whilst I had hoped for more, I still
think this direction is the right one and the changes are worth
pursuing.
Cheers,
Richard
parent reply other threads:[~2023-01-04 16:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <173725B379431FBC.11747@lists.openembedded.org>]
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=4a8cbda140f676a63cff3e13678bcd8407ef50dd.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.