On Thu, Mar 19, 2020 at 9:07 AM Mike Looijmans <[email protected]> wrote: > > On 19-03-2020 12:04, Richard Purdie via Lists.Yoctoproject.Org wrote: > >> , fetch, configure, package and rootfs tasks. > > > > Sadly these tasks are much harder. > > It would be really great if some sort of "weight" could be attached to a > task. This relates to memory usage. > > My system has 16 cores but only 8GB RAM. With both parallelization > options to "16", I might end up with 16 compile tasks running 16 compile > threads each, i.e. 256 running processes. In practice this doesn't > actually happen, but the memory load gets high sometimes, so I reduce > the TASKS to 8 at most. That has kept my system out of swap trouble for > the time being. > > The idea was that tasks get a "weight" in terms of cores they'll use, > and the scheduler takes that into account. So it would run 16 > do_configure tasks (weight=1) in parallel, but it would not start a new > task that would push the weight over some number (say 40 for my case). > So it would start a third compile, but not a fourth, but it would start > a do_configure task. > > Does that make sense? >
is it something like make -l ? that you are looking for here. > In builds involving FPGA's I have tasks that take up about 48GB of RAM > (my machine cannot run them) but only a single CPU core. Attempting to > run multiple of these in parallel (happened to me when I changed some > shared recipe content) will bring most machines to their knees. > Currently my only way of handling that is manual interference... > > -- > Mike Looijmans >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48866): https://lists.yoctoproject.org/g/yocto/message/48866 Mute This Topic: https://lists.yoctoproject.org/mt/72047879/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
