Re: What are the key factors for yocto build speed?
On Thu, Mar 19, 2020 at 11:04:26AM +0000, Richard Purdie wrote:
On Thu, 2020-03-19 at 08:05 +0000, Mikko Rapeli wrote:I will double check, but I'm sure I see IO going to disk when plenty of RAMOnce this is done, IO still happens when anything calls sync() andDoesn't pseudo intercept and stop these sync calls already? Its
is still available in page cache.
I'm not fully aware what bitbake does before starting task execution.The effect is clearly visible during build time using Performance Co-Recipe parsing should hit 100% CPU, its one of the few places we can do
With sumo, there is an initial spike in CPU use and then a long single
thread wait where log shows "Initialising tasks..." and Cooker process
is using a single core. For me this takes at least one minutes for
every build. Same is visible with zeus too.
Example graph from pmchart:
Yep., fetch, configure, package and rootfs tasks.Sadly these tasks are much harder.
I'll try to check this case once more.Memory is not fully utilized either since IO through sync()/fsync()non-pseudo tasks?