All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Markus Lehtonen <markus.lehtonen@linux.intel.com>, poky@yoctoproject.org
Subject: Re: [PATCH 3/3] bb-perf: plot histograms base on buildstats data
Date: Wed, 16 Nov 2016 16:44:47 -0600	[thread overview]
Message-ID: <def34d22-e7ec-b6d6-13bc-0ae44be7c23d@linux.intel.com> (raw)
In-Reply-To: <1479291900.13463.4.camel@linux.intel.com>



On 11/16/2016 04:25 AM, Markus Lehtonen wrote:
> On Tue, 2016-11-15 at 15:19 -0600,
> leonardo.sandoval.gonzalez@linux.intel.com wrote:
>> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
>>
>> Scripts that produces script data to be consumed by gnuplot.
>> There are two possible plots depending if either the
>> -S parameter is present or not:
>>
>>      * without -S: Produces a histogram listing top N recipes/tasks versus
>>        stats. The first stat defined in the -s parameter is the one taken
>>        into account for ranking
>>      * -S: Produces a histogram listing tasks versus stats.  In this case,
>>        the value of each stat is the sum for that particular stat in all
>> recipes found.
>>        Stats values  are in descending order defined by the first stat
>> defined on -s
>>
>> EXAMPLES
>>
>> 1. Top recipes' tasks taking into account utime
>>
>>      $ buildstats-plot.sh -s utime | gnuplot -p
>>
>> 2. Tasks versus utime:stime
>>
>>      $ buildstats-plot.sh -s utime:stime -S | gnuplot -p
>>
>> 3. Tasks versus IO write_bytes:IO read_bytes
>>
>>      $ buildstats-plot.sh -s 'IO write_bytes:IO read_bytes' -S | gnuplot
>> -p
> One problem (or problematic restriction) I see is that the script relies on
> the new buildstats format introduced by PATCH 2/3 in this patchset, making
> the script incompatible with older buildstats and not being able to render
> them.

The proposed buildstats.sh script has the same behavior as the old one 
if -s 'Elapsed time' is included as argument. The new feature introduced 
is that we can parse other stats besides Elapsed Time, so with 
buildstats-plot.sh can make use of it. The main reason of the 2/2 change 
is that Elapsed time does not give us much info because this is wall 
time, not CPU time.

> Another problem for me is the dependency on datamash which I wasn't able to
> find for my distro (openSUSE Leap 42.1). How hard would it be to ditch the
> dependency on datamash?
datamash is pretty good for doing basic stat and this case we are just 
summing columns by 'groups'. The same thing can be with awk of course. 
Looking at the https://www.gnu.org/software/datamash/download/, there is 
no package ready for opensuse so the only option here is to get the 
tarball and 'make' it.


> Thanks,
>    Markus
>
>



  reply	other threads:[~2016-11-16 22:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 21:19 [PATCH 0/3] bb-perf: scripting to plot buildstats data leonardo.sandoval.gonzalez
2016-11-16 23:05 ` leonardo.sandoval.gonzalez
2016-11-15 21:19 ` [PATCH 1/3] buildstats: Place 'Elapsed Time' stat into a single line leonardo.sandoval.gonzalez
2016-11-16 23:05   ` leonardo.sandoval.gonzalez
2016-11-15 21:19 ` [PATCH 2/3] scripts: Specify the stats to take into account leonardo.sandoval.gonzalez
2016-11-16 23:05   ` leonardo.sandoval.gonzalez
2016-11-15 21:19 ` [PATCH 3/3] bb-perf: plot histograms base on buildstats data leonardo.sandoval.gonzalez
2016-11-16 23:05   ` leonardo.sandoval.gonzalez
2016-11-16 10:25   ` Markus Lehtonen
2016-11-16 22:44     ` Leonardo Sandoval [this message]
2016-11-16 11:53 ` [PATCH 0/3] bb-perf: scripting to plot " Richard Purdie
2016-11-16 22:48   ` Leonardo Sandoval

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=def34d22-e7ec-b6d6-13bc-0ae44be7c23d@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=markus.lehtonen@linux.intel.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.