<div dir="ltr">On Tue, 13 Aug 2019 at 11:04, Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>> wrote:<br><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">We talked on irc and you pointed at the commit things started to go<br>
wrong. Just to summarise things for the benefit of the list, this is<br>
some quick testing I did:<br>
<br>
"bitbake -p; time bitbake core-image-minimal -n"<br>
<br>
30.0s 6c7c0cefd34067311144a1d4c01986fe0a4aef26<br>
30.6s a0d941c787cf3ef030d190903279d311bc05d752<br>
40.3s 7df31ff36892c2f9c65326b06b4c70 <br>
42.2s a0542ed3ff700eca35f9195f743c9e28bcd50f3e <br>
45.4s 9983b07fffd19082abded7c3f15cc77d306dd69c <br>
76.9s master-next<br>
<br>
So basically the original changes showed a 25% hit but the performance<br>
of -next is dire.<br></blockquote><div><br></div><div>Sadly with larger sets the performance hit is much worse. I enabled all of the layers in meta-oe, and ran this with empty sstate and build directories:<br></div><div></div><div>bitbake -p; time bitbake -n -k world <br></div><div><br></div><div>The outcomes are:</div><div></div><div><div dir="ltr"><br></div><div dir="ltr">6c7c0cefd34067311144a1d4c01986fe0a4aef26<br></div><div dir="ltr">12m51,848s</div>(this is the baseline; the bulk of the time goes towards going through the task list without executing the tasks - the 'spinning task counter" part)<br></div><div><br></div><div>9983b07fffd19082abded7c3f15cc77d306dd69c</div><div>66m29,563s</div><div><br></div><div>So there could be something quadratically-growing going on with these new commits :(<br></div><div><br></div><div>I didn't dare to try master-next after seeing above how it hits core-image-minimal and master already regressing to over an hour :-(</div><div><br></div><div>Alex<br> </div></div>
</div>