On Wed, 14 Aug 2019 at 13:36, <[email protected]> wrote:
> On Wed, 2019-08-14 at 13:25 +0200, Alexander Kanavin wrote: > > On Tue, 13 Aug 2019 at 21:18, Richard Purdie < > > [email protected]> 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)) > > ? > Even crazier is the outcome: it helped! The whole thing completed after 15m49secons (with much of the time going to the empty task spin), that's some 3 minutes slower, but certainly it's usable again. I have not enabled the hash server at any point. Alex
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
