<div dir="ltr"><div dir="ltr">On Wed, 14 Aug 2019 at 23:25, <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Right, it still definitely needs work. Its a balancing act between<br>
sorting out the execution bugs in the code and figuring out the<br>
performance problem.<br>
<br>
If anyone wants to experiment, the way I'd debug this is to run the<br>
before and after cases with the -P option to bitbake. If you want to<br>
exit early just make the code return where it prints "Executing tasks"<br>
or whatever makes sense as Ctrl+C won't write the profile data.<br>
<br>
You want the profile.log.processed file.<br>
<br>
So save that file with the "before" commit, then save it afterwards and<br>
look at those files and see where its spending more time.<br>
<br>
If someone generates those two files I'll happily take a look, I'm kind<br>
of used to reading them. There are four sets of output in there, same<br>
data but different sorting/types, each has its uses.<br></blockquote><div><br></div><div>And here they are (with task spinning included this time):</div><div><a href="http://sensi.org/~ak/tmp/profile.log.processed.before">http://sensi.org/~ak/tmp/profile.log.processed.before</a></div><div><a href="http://sensi.org/~ak/tmp/profile.log.processed.after">http://sensi.org/~ak/tmp/profile.log.processed.after</a></div><div><br></div><div>Hope you find it useful!</div><div><br></div><div>Alex<br> </div></div></div>