Ask HN: Why is Yocto so slow but so popular?

Re:Ask HN: Why is Yocto so slow but so popular? by not_your_vase on Thursday January 16, 2025 @06:59AM (#42724165)

I'm quite heavily invested in Yocto, both professionally and on hobby level. Not saying that bitbake is blazing fast, but these minutes long parsing and init steps will be something specific to your machine. On my home desktop (Ryzen 5600G + 32GB RAM) Bitbake init including all parsing doesn't take more than 10 sec. It is similar on my laptop (Ryzen 4700U + 16GB RAM).

It takes only more if I change some global config, but even then parsing doesn't take more than 40-50 seconds, before it would actually start cranking on the tasks.

Have you tried asking around the Yocto mailing list?

[ Parent | on HN ]

Re:Ask HN: Why is Yocto so slow but so popular? by c0deR3D on Thursday January 16, 2025 @09:11AM (#42725320)

Your scenario makes me suspecting that it is Xilinx flavored Yocto causing the problem. I think that removing some unused Xilinx-specific layers/recipes can reduce the prologue and epilogue execution time.

[ Parent | on HN ]

Re:Ask HN: Why is Yocto so slow but so popular? by not_your_vase on Thursday January 16, 2025 @12:20PM (#42728106)

Well, Xilinx layers are definitely not the most light-weight ones, though they still shouldn't cause parsing/task init to take minutes. By any chance, are you using WSL? I have heard some complaints about storage I/O performance, when it comes to this...

[ Parent | on HN ]

Re:Ask HN: Why is Yocto so slow but so popular? by c0deR3D on Thursday January 16, 2025 @07:38PM (#42732759)

Nope, mine runs on a native Linux box featuring Intel i7-1370P and 32GB RAM. Maybe Xilinx has some tuning which makes Yocto become slow at parsing the recipe dependency and the likes.

I've tried asking the Xilinx community, and got only a reply saying that there is a database in Yocto which limits the scalability.

[ Parent | on HN ]