From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 0/4] Use buildstats from OE to generate build charts
Date: Tue, 14 Sep 2021 10:18:23 +0300 [thread overview]
Message-ID: <3292485.LZWGnKmheA@home> (raw)
In-Reply-To: <8873b8d9-da7a-ea8b-6565-72f7690e5cf8@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
In the email from понедельник, 13 сентября 2021 г. 21:23:01 +03 user Jan
Kiszka wrote:
> On 13.09.21 17:03, Uladzimir Bely wrote:
> > OE uses buildstats to analyze build performance. This patchset ports
> > this functionality to Isar.
> >
> > Build statistics is collected in $BUILDDIR/tmp/buildstats and can be
> > converted to PDF file or viewed directly.
>
> Do you have some example to share? What can be done with those stats?
> Any insights they already provided on the isar build itself?
>
> Jan
>
Yes, I've attached a resulting PDF file.
The files with statistics (per-task) look like:
> # cat tmp/buildstats/20210911054429/libhello-0.1-98f2e41-r0/do_dpkg_build
> Event: TaskStarted
> Started: 1631339274.20
> libhello-0.1-98f2e41-r0: do_dpkg_build
> Elapsed time: 23.14 seconds
> utime: 5
> stime: 1
> cutime: 296
> cstime: 60
> IO rchar: 68567001
> IO wchar: 8422571
> IO syscr: 38933
> IO syscw: 13329
> IO read_bytes: 12288
> IO write_bytes: 7458816
> IO cancelled_write_bytes: 2174976
> rusage ru_utime: 0.058727999999999995
> rusage ru_stime: 0.010676999999999999
> rusage ru_maxrss: 35348
> rusage ru_minflt: 5000
> rusage ru_majflt: 0
> rusage ru_inblock: 0
> rusage ru_oublock: 96
> rusage ru_nvcsw: 238
> rusage ru_nivcsw: 0
> Child rusage ru_utime: 2.966387
> Child rusage ru_stime: 0.609613
> Child rusage ru_maxrss: 33004
> Child rusage ru_minflt: 552727
> Child rusage ru_majflt: 0
> Child rusage ru_inblock: 24
> Child rusage ru_oublock: 14472
> Child rusage ru_nvcsw: 9123
> Child rusage ru_nivcsw: 507
> Status: PASSED
> Ended: 1631339297.35
--
Uladzimir Bely
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
[-- Attachment #2: build.pdf --]
[-- Type: application/pdf, Size: 33473 bytes --]
next prev parent reply other threads:[~2021-09-14 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 15:03 Uladzimir Bely
2021-09-13 15:03 ` [PATCH 1/4] buildstats: Borrow buildstats and pybootchartgui from OE Uladzimir Bely
2021-09-13 15:03 ` [PATCH 2/4] buildstats: Fix bbclass to work with ISAR Uladzimir Bely
2021-09-13 15:03 ` [PATCH 3/4] buildstats: Manage buildstats via USER_CLASSES variable Uladzimir Bely
2021-09-13 15:03 ` [PATCH 4/4] doc: Add buildstats section in user manual Uladzimir Bely
2021-09-13 18:23 ` [PATCH 0/4] Use buildstats from OE to generate build charts Jan Kiszka
2021-09-14 7:18 ` Uladzimir Bely [this message]
2021-09-14 11:23 ` Jan Kiszka
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=3292485.LZWGnKmheA@home \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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