<div dir="ltr"><div dir="ltr">On Tue, 13 Aug 2019 at 21:18, Richard Purdie <<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">I had a glance at the profile output from master-next and the problem<br>
wasn't where I thought it would be, it was in the scheduler code. That<br>
is good as those classes are effectively independent of the other<br>
changes and hence are a separate fix.<br>
<br>
I've put a patch in -next which takes the above test to 36s which is<br>
close to the older bitbake.<br>
<br>
Could be interesting to see how it looks for others and different<br>
workloads.<br></blockquote><div><br></div><div>I just tried the same test I did yesterday with ab56d466452148e5fce330d279d13e2495eceb1f. Unfortunately it doesn't seem to improve things much: bitbake is stuck at "NOTE: Executing Tasks" for 15 minutes now.</div><div><br></div><div>Alex<br> </div></div></div>