From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Build time graph generation
Date: Mon, 10 Oct 2011 16:20:16 +0200 [thread overview]
Message-ID: <20111010162016.55214e4e@skate> (raw)
In-Reply-To: <CAAXf6LUGVEGBy2hGA8g0_NdqSb72+rOKbnU9x7+rWOoTmV8hvg@mail.gmail.com>
Thomas,
Le Mon, 10 Oct 2011 15:55:49 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> > I don't think the modification to the package infrastructure is ready
> > for merging (there are many cases not handled, like when the timing
> > data should be cleaned up, the case of overriden packages not being
> > handled, etc.) and I am not even sure it is useful to complicate the
> > package infrastructure with such a not-so-useful feature.
>
> I like the idea of having such information, so I'm in favor of these patches.
Thanks :-)
Though I'm still not sure of how they can be useful.
> (The graphs also painfully show the time lost in all ./configure
> steps, while many of the checks are identical...)
In the past, we did try to improve that situation by using the
"configure cache" mechanism, thanks to which configure checks done by
past configure script executions are used to speed up the execution of
future configure scripts (since as you say, they all do mostly the same
checks). Unfortunately, the configure scripts aren't that standardized
and they store the result of different checks in variables of the same
name, resulting to many strange problems. We had this feature enabled
by default in Buildroot for a while (even in stable releases if I'm
correct), but in the end, we dropped it because it was very complicated
to stabilized (we already had to patch multiple configure.{in,ac}
files).
> As I mentioned as comment on your patch, I think we can make this an
> optional feature for those who want it.
Yes, sure.
> Is it possible to have html output as an alternative to pdf? I can
> also imagine that some people simply want image files, like png or
> even svg, so the graphs can easily be embedded in other web pages.
Generating PNG or SVG with matplotlib is definitely possible. I'm not
sure about HTML though, do you mean a webpage that simply includes the
four graphs?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-10 14:20 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
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 [this message]
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=20111010162016.55214e4e@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox