Re: Timing a recipe


Ross Burton
 

As said, buildstats is *exactly* what you want. There's a forked
pybootchart in oe-core that can visualise the data too.

Ross

On Mon, 15 Feb 2021 at 20: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.



Join yocto@lists.yoctoproject.org to automatically receive all group messages.