On Thu, 2023-09-14 at 12:35 +0000, Dave Hitchman wrote: > > Does anyone know what IS enough? Watching the video series > around https://www.youtube.com/watch?v=bTEdfwtPtNY he doesnt mention > changing this size. I dont actually know what this watch manager > thing is supposed to be doing, there is one command prompt doing one > thing, I cant believe that it would need that many things being > watched? What is it even watching for?
There is a "memory resident" mode for bitbake (BB_SERVER_TIMEOUT = "X") and for that to work reliably, bitbake needs to know when to reparse metadata. For that reason it does track the metadata changing. In theory it does this even when not staying resident so it can detect changes in the metadata during builds and inform the user not to do that and also to reduce differences in the codepaths between memory resident and non-resident codepaths. You might think 65k sounds a lot but in a simple OE-Core checkout, there are 2.5k directories and 19k files. In order to reduce system impact, bitbake only monitors directories, not files. I'd imagine somehow you have a lot of directories being included in the watch paths. FWIW in a given build there are millions of files being processed. We should only be monitoring the recipe/config files though. So whilst that doesn't answer your question fully and I don't know where the files are coming from, 65k is a relatively easy number to reach in the kinds of work bitbake does. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61007): https://lists.yoctoproject.org/g/yocto/message/61007 Mute This Topic: https://lists.yoctoproject.org/mt/101356635/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
