On Wed, 2019-08-14 at 13:25 +0200, Alexander Kanavin wrote: > On Tue, 13 Aug 2019 at 21:18, Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > > I had a glance at the profile output from master-next and the > > problem > > wasn't where I thought it would be, it was in the scheduler code. > > That > > is good as those classes are effectively independent of the other > > changes and hence are a separate fix. > > > > I've put a patch in -next which takes the above test to 36s which > > is > > close to the older bitbake. > > > > Could be interesting to see how it looks for others and different > > workloads. > > 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.
This might sound slightly crazy but can you try commenting out this line in runqueue.py: logger.debug(2, "Holding off tasks %s" % pprint.pformat(self.holdoff_tasks)) ? This was with the hash server disabled, right? Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
