All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konrad Weihmann" <kweihmann@outlook.com>
To: yocto@lists.yoctoproject.org, rustyhowell@gmail.com
Subject: Re: [yocto] Timing a recipe
Date: Mon, 15 Feb 2021 21:12:04 +0100	[thread overview]
Message-ID: <AM9PR09MB4642A3B12B44A1F158613D13A8889@AM9PR09MB4642.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <fQ55.1613419717498551221.Ltf0@lists.yoctoproject.org>

buildstats [1] maybe? That can be inherited globally and does give some 
neat results and insights

[1] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/buildstats.bbclass

On 15.02.21 21:08, rustyhowell@gmail.com wrote:
> Is there a way to automatically record build time of a recipe without 
> modifying the recipe itself?  I have a recipe that is a monster, it has 
> many git URIs and produces many packages that are coupled. It should be 
> broken up but company deadlines have kept us from taking the time to do 
> this. I was talking to my boss about this. He said we really needs some 
> concrete data about how much this monster recipe is costing us before 
> green-lighting the massive effort to split up the recipe.  I agree with 
> him, so I would like to know how much time is spent repeatedly building 
> this recipe.  I figure I could do this by adding do_fetch_prepend() and 
> writing the time to a file, and then do_install_append() and writing the 
> time to the file. So after a week or so, I would have many start/end 
> data points to discuss.
> 
> However, I did not want to modify the recipe itself. I was hoping to 
> augment the recipe via local.conf. Another bbappend in a new layer would 
> work I guess, but I was hoping there was something simpler. Thanks in 
> advance.
> 
> 
> 
> 
> 

  reply	other threads:[~2021-02-15 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 20:08 Timing a recipe rustyhowell
2021-02-15 20:12 ` Konrad Weihmann [this message]
2021-02-16  6:11   ` [yocto] " Yocto
2021-02-16 19:43     ` rustyhowell
2021-02-16 20:04       ` [yocto] " Khem Raj
2021-02-17 12:55       ` Richard Purdie
2021-02-17 11:32 ` Ross Burton

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=AM9PR09MB4642A3B12B44A1F158613D13A8889@AM9PR09MB4642.eurprd09.prod.outlook.com \
    --to=kweihmann@outlook.com \
    --cc=rustyhowell@gmail.com \
    --cc=yocto@lists.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.