05-18, 13:45–14:00 (UTC), Kirkstone
In this talk we will discuss detailed analysis of the Yocto build on the resource-per-tool level. Understanding where the time goes in a build and what are the bottlenecks in your implementation can help with choosing the right sizing for your build machine or build grid.
Using the example of an Automotive Grade Linux build, We will analyze actual CPU time spent on compiling, packaging and performing other common tasks, gaining insights on what makes builds take as much as they do, which build-time resource constraints exist, and how they could be alleviated.
In this talk we will discuss detailed analysis of the Yocto build on the resource-per-tool level. Understanding where the time goes in a build and what are the bottlenecks in your implementation can help with choosing the right sizing for your build machine or build grid.
Using the example of an Automotive Grade Linux build, We will analyze actual CPU time spent on compiling, packaging and performing other common tasks, gaining insights on what makes builds take as much as they do, which build-time resource constraints exist, and how they could be alleviated.
Amir Kirsh is a C++ lecturer at the Academic College of Tel-Aviv-Yaffo and at Tel-Aviv University, previously the Chief Programmer at Comverse, after being CTO and VP R&D at a startup acquired by Comverse. He is also a co-organizer of the annual Core C++ conference and a member of the ISO C++ Israeli National Body. Recently Amir joined Incredibuild as a C++ Dev Advocate.