linux/poky.git/scripts/pybootchartgui, branch 2.6_M3

pybootchartgui: support reading reduced /proc logs

2016-12-07T10:38:00+00:00

Pre-processing /proc data during the build considerably reduces the amount of data written to disk: 176KB instead of 4.7MB for a 20 minuted build. Parsing also becomes faster. buildstats.bbclass only writes the reduced logs now, but support for the full /proc files is kept around as reference. (From OE-Core rev: b5e47df9af1ebbb477074587fdeae17eb2f55582) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui: simplify drawing of memory usage

2016-12-07T10:37:59+00:00

The internal representation after parsing now matches exactly what the drawing code needs, thus speeding up drawing a bit. However, the main motivation is to store exactly that required information in a more compact file. (From OE-Core rev: ca06e67a0bb5820b38fda4c8dfee20764c1e59ae) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui: render disk space usage

2016-12-07T10:37:59+00:00

This adds a new, separate chart showing the amount of disk space used over time for each volume monitored during the build. The hight of the graph entries represents the delta between current usage and minimal usage during the build. That's more useful than showing just the current usage, because then a graph showing changes in the order of MBs in a volume that is several GB large would be just flat. The legend shows the maximum of those deltas, i.e. maximum amount of space needed for the build. Minor caveat: sampling of disk space usage starts a bit later than the initial task, so the displayed value may be slightly lower than the actual amount of space needed because sampling does not record the actual initial state. (From OE-Core rev: 263d189d066b578debf08b2bd07494a69b70f70d) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui/parsing.py: fix error handling in meminfo parser

2016-12-07T10:37:59+00:00

When matching fails, m.group(0) is invalid and can't be used in the error message. (From OE-Core rev: ddfea21e06a2e6b1a1e766969f8c134a6de7388a) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui/draw.py: skip empty CPU and disk usage charts

2016-12-07T10:37:59+00:00

The only real change is the addition of two if checks that skips the corresponding drawing code when there is no data. (From OE-Core rev: 1658fd5e9ca1ba793cae604c2a395d54e3ec9056) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui: show system utilization

2016-12-07T10:37:59+00:00

This enables rendering of the original bootchart charts for CPU, disk and memory usage. It depends on the /proc samples recorded by the updated buildstats.bbclass. Currently, empty charts CPU and disk usage charts are drawn if that data is not present; the memory chart already gets skipped when there's no data, which will also have to be added for the other two. (From OE-Core rev: 233d3e50b361feea07803a9c0f2a691e687c6cd5) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui/draw.py: fix drawing of samples not starting at zero

2016-12-07T10:37:59+00:00

The code did not handle x scaling correctly when drawing starts at some time larger than zero, i.e. it worked for normal bootchart data, but not for the system statistics recorded by buildstats.bbclass. (From OE-Core rev: 166f8f9aaa1f01fc6d6a5451f8f06b815c51ffae) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pybootchartgui/draw.py: allow moving process chart up and down

2016-12-07T10:37:59+00:00

Substracting curr_y when determining the hight of the process chart is wrong because the height is independent of the position where the chart is about to be drawn. It happens to work at the moment because curr_y is always 10 when render_processes_chart() gets called. But it leads to a negative height when other charts are drawn above it, and then the grid gets drawn on top of those other charts. Substracting some constant is relevant because otherwise the box is slightly larger than the process bars. Not sure exactly where that comes from (text height?); leg_s seems a suitable constant and happens to be 10, so everything still gets rendered exactly as before. (From OE-Core rev: b6bb690728c329ae448f89a1b68298c6dd8a573a) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

scripts/pybootchart: Fix print statement

2016-06-03T13:38:01+00:00

This was broken with the python3 fixes. (From OE-Core rev: 0eadd008d08f9a6bb17a1f641b4735d0d2012580) Signed-off-by: Richard Purdie

scripts: python3: get rid of future imports

2016-06-03T12:13:29+00:00

Removed print_function and with_statement imports from __future__ as they're supported by python 3 by default. (From OE-Core rev: 77ae2daad5d775d710b953cf0c623ce74cb2c274) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

linux/poky.git/scripts/pybootchartgui, branch 2.6_M3

pybootchartgui: support reading reduced /proc logs

pybootchartgui: simplify drawing of memory usage

pybootchartgui: render disk space usage

pybootchartgui/parsing.py: fix error handling in meminfo parser

pybootchartgui/draw.py: skip empty CPU and disk usage charts

pybootchartgui: show system utilization

pybootchartgui/draw.py: fix drawing of samples not starting at zero

pybootchartgui/draw.py: allow moving process chart up and down

scripts/pybootchart: Fix print statement

scripts: python3: get rid of __future__ imports

scripts: python3: get rid of future imports