From: "Sakib Sajal" <sakib.sajal@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] buildstats.bbclass: add functionality to collect
Date: Fri, 23 Oct 2020 12:56:47 -0400 [thread overview]
Message-ID: <20201023165648.5515-1-sakib.sajal@windriver.com> (raw)
This functionality allows users to log host stats on a regualar
interval and/or upon failure.
Initial implementation design was to predefine a list of commands
to collect host system stats.
Obstacles:
Event TaskFailed runs in recipe specific environments, ie, the PATH
variable does not point to host tools. Moreover, having a predefined
list of tools to run is rigid and many of the tools may not be
available on the host system.
Solution:
Allow users to specify the tools with the absolute path, as well as
the desired options to be run. The onus is on the users to make sure the
tools exist and the command runs to completion and exits.
Built core-image-minimal with an interval of 10s which resulted in a
log file of size 15Mb at a cost of 1-2% increase in build time.
core-image-minimal tmp-glibc is ~20Gb, and this increase is a trivial
increase.
Grepping the log file for specific tokens give a useful indication of
how the system resources are being used.
To Do:
1) Do selftests need to be added for this functionality?
2) Documentation about the usage.
Sakib Sajal (1):
buildstats.bbclass: add functionality to collect build system stats
meta/classes/buildstats.bbclass | 33 ++++++++++++++++++++++++++++++---
1 file changed, 30 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-23 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 16:56 Sakib Sajal [this message]
2020-10-23 16:56 ` [PATCH 1/1] buildstats.bbclass: add functionality to collect build system stats Sakib Sajal
2020-10-23 17:25 ` [OE-core] " Christopher Larson
2020-10-23 18:58 ` Sakib Sajal
2020-10-28 14:27 ` Richard Purdie
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=20201023165648.5515-1-sakib.sajal@windriver.com \
--to=sakib.sajal@windriver.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