From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Watt <jpewhacker@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] initscripts: populate-volatiles: Speed up processing
Date: Fri, 12 Oct 2018 08:33:43 +0100 [thread overview]
Message-ID: <7fe513b6dcb00e887b7fce35e25ff74cff263070.camel@linuxfoundation.org> (raw)
In-Reply-To: <20181011180843.13983-1-JPEWhacker@gmail.com>
On Thu, 2018-10-11 at 13:08 -0500, Joshua Watt wrote:
> Checking the requirements for each volatiles file in the
> populate-volatiles script can be very slow when there are a large
> number
> of volatiles files, easily consuming over 80% of the processing time.
> These checks don't usually uncover any problems so concatenate all
> the
> volatiles files together and process them as one large file for a
> "fast
> path" option. This ensures that the penalty for checking the
> requirements is only incurred once. In the event that checking the
> requirements for the unified file fails, fall back to the slow
> process
> of checking each one individually so that the offending one can be
> skipped.
>
> [YOCTO #12949]
>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
As yet I little evidence for it but I think this caused:
https://autobuilder.yoctoproject.org/typhoon/#/builders/35/builds/69/steps/7/logs/step6c
You can see the config in:
https://autobuilder.yoctoproject.org/typhoon/#/builders/35/builds/69/steps/7/logs/stdio
the key bits for 6c are:
DISTRO_FEATURES_append = ' systemd'
VIRTUAL-RUNTIME_init_manager = 'sysvinit'
Cheers,
Richard
next prev parent reply other threads:[~2018-10-12 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:08 [PATCH] initscripts: populate-volatiles: Speed up processing Joshua Watt
2018-10-12 7:33 ` Richard Purdie [this message]
2018-10-12 15:39 ` Joshua Watt
2018-10-12 16:24 ` [PATCH v2] " Joshua Watt
2018-10-18 8:01 ` Mike Looijmans
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=7fe513b6dcb00e887b7fce35e25ff74cff263070.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jpewhacker@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox