All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package: instrument to gather timing data
Date: Tue, 11 Oct 2011 18:12:06 +0200	[thread overview]
Message-ID: <201110111812.06508.arnout@mind.be> (raw)
In-Reply-To: <CAAXf6LXtCXk4c83xZK9os2Px9+Y2LzGnFxBt6h4puNEx-8F3dA@mail.gmail.com>


On Tuesday 11 October 2011 10:29:13, Thomas De Schampheleire wrote:
> >> and the build-time.data is
> >> never removed, so results will accumulate if several partial builds
> >> are done.
> > 
> > I would call that a feature :-) Partial builds typically mean that you're
> > hacking away at some package, and then it's very relevant to see the
> > impact on build time.
> 
> How would you see the impact? Wouldn't it be more useful to save the
> timing data for subsequent runs in different files (e.g. timestamped
> files) so that you can compare such runs?
> If you let the data accumulate, you'd get one big number for each
> step/package combination, unless you're going to update the parser
> script to display the different data lines as separate entities, one
> for each run).

 I hadn't read the parser script, I assumed it would just generate a different 
bar for each run.  Now I see it would only work in pie-steps mode.

 BTW, histogram is a wrong name.  A histogram would for instance indicate how 
many packages have a build time between 1 and 2 seconds.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111011/6c5aa6d8/attachment.html>

  reply	other threads:[~2011-10-11 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 16:17 [Buildroot] [RFC] Build time graph generation Thomas Petazzoni
2011-10-09 16:17 ` [Buildroot] [PATCH 1/2] package: instrument to gather timing data Thomas Petazzoni
2011-10-10 13:41   ` Thomas De Schampheleire
2011-10-11  5:59     ` Arnout Vandecappelle
2011-10-11  5:59   ` Arnout Vandecappelle
2011-10-11  7:34     ` Thomas Petazzoni
2011-10-11  8:29     ` Thomas De Schampheleire
2011-10-11 16:12       ` Arnout Vandecappelle [this message]
2011-10-11 18:17         ` Thomas Petazzoni
2011-10-09 16:17 ` [Buildroot] [PATCH 2/2] graph-build-time: generate graphs based on " Thomas Petazzoni
2011-10-10 13:12   ` Thomas De Schampheleire
2011-10-10  9:32 ` [Buildroot] [RFC] Build time graph generation Diego Iastrubni
2011-10-10 13:55 ` Thomas De Schampheleire
2011-10-10 14:20   ` Thomas Petazzoni
2011-10-10 15:19     ` Thomas De Schampheleire

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=201110111812.06508.arnout@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.