Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/11] system statistics sampling
Date: Mon, 28 Nov 2016 16:33:03 +0100	[thread overview]
Message-ID: <cover.1480346284.git.patrick.ohly@intel.com> (raw)

These patches depend on the corresponding patches to bitbake.

buildstats.bbclass gets extended so that disk bandwidth and capacity,
CPU and memory usage get sampled at regular time intervals by
default. pybootchart had code for most of that data, which gets
restored and re-enabled. The disk capacity graph is new.

The original pybootchart just stored raw dumps of the special files
under /proc. bitbake builds run longer, so a more compact ("reduced")
format is used.

Logging disk capacity was mostly motivated by some work on enhancing
rm_work.bbclass behavior, but could also be useful for others ("how
much free space did my build need").

The following changes since commit 9f1fe76727e98e58fc9e46ea2b49cf5c0cb48e6c:

  libpcap: Fix build when PACKAGECONFIG ipv6 is not enable (2016-11-23 11:02:33 +0000)

are available in the git repository at:

  git://github.com/pohly/openembedded-core buildstats
  https://github.com/pohly/openembedded-core/tree/buildstats

Patrick Ohly (11):
  buildstats: add system state sampling
  pybootchartgui/draw.py: allow moving process chart up and down
  pybootchartgui/draw.py: fix drawing of samples not starting at zero
  pybootchartgui: show system utilization
  pybootchartgui/draw.py: skip empty CPU and disk usage charts
  buildstats: record disk space usage
  pybootchartgui/parsing.py: fix error handling in meminfo parser
  pybootchartgui: render disk space usage
  pybootchartgui: simplify drawing of memory usage
  buildstats: reduce amount of data stored for system utilization
  pybootchartgui: support reading reduced /proc logs

 meta/classes/buildstats.bbclass                  |  16 ++
 meta/lib/buildstats.py                           | 156 ++++++++++++++++++
 scripts/pybootchartgui/pybootchartgui/draw.py    | 192 ++++++++++++++++-------
 scripts/pybootchartgui/pybootchartgui/parsing.py | 122 +++++++++++---
 scripts/pybootchartgui/pybootchartgui/samples.py |  27 ++++
 5 files changed, 435 insertions(+), 78 deletions(-)
 create mode 100644 meta/lib/buildstats.py

-- 
2.1.4



             reply	other threads:[~2016-11-28 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 15:33 Patrick Ohly [this message]
2016-11-28 15:33 ` [PATCH 01/11] buildstats: add system state sampling Patrick Ohly
2016-12-09  0:29   ` Andreas Oberritter
2016-12-09  7:55     ` Patrick Ohly
2016-12-09  7:57     ` Patrick Ohly
2016-11-28 15:33 ` [PATCH 02/11] pybootchartgui/draw.py: allow moving process chart up and down Patrick Ohly
2016-11-28 15:33 ` [PATCH 03/11] pybootchartgui/draw.py: fix drawing of samples not starting at zero Patrick Ohly
2016-11-28 15:33 ` [PATCH 04/11] pybootchartgui: show system utilization Patrick Ohly
2016-11-28 15:33 ` [PATCH 05/11] pybootchartgui/draw.py: skip empty CPU and disk usage charts Patrick Ohly
2016-11-28 15:33 ` [PATCH 06/11] buildstats: record disk space usage Patrick Ohly
2016-11-28 15:33 ` [PATCH 07/11] pybootchartgui/parsing.py: fix error handling in meminfo parser Patrick Ohly
2016-11-28 15:33 ` [PATCH 08/11] pybootchartgui: render disk space usage Patrick Ohly
2016-11-28 15:33 ` [PATCH 09/11] pybootchartgui: simplify drawing of memory usage Patrick Ohly
2016-11-28 15:33 ` [PATCH 10/11] buildstats: reduce amount of data stored for system utilization Patrick Ohly
2016-11-28 15:33 ` [PATCH 11/11] pybootchartgui: support reading reduced /proc logs Patrick Ohly

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=cover.1480346284.git.patrick.ohly@intel.com \
    --to=patrick.ohly@intel.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