The only task that I see taking really long is the do_rootfs. And I think that it takes that long because disks are slooow :)
2016-07-04 20:14 GMT-03:00 Takashi Matsuzawa <tmatsuz...@uievolution.com>: > By the way, PyPy seems to have some restriction that is not fully compatible > with CPyhon and bitbake scripts may not run as they are. I tried it > yesterday and learned that it is not a simple in-place replacement. > > > > ________________________________ > From: Burton, Ross <ross.bur...@intel.com> > Sent: Tuesday, July 5, 2016 3:50 AM > To: Marcelo E. Magallon > Cc: Takashi Matsuzawa; yocto@yoctoproject.org > Subject: Re: [yocto] Shorter build time? > > > On 4 July 2016 at 19:10, Marcelo E. Magallon <marcelo.magal...@hpe.com> > wrote: >> >> That is true, but I've seen cases where the start up time of Python (or >> the time it takes bitbake to start "doing work") is *perceptually* much >> larger than the work done by the recipe, or at least it looks like it >> represents a sigficant fraction of the total work. That's where PyPy >> might help. > > > Measuring that overhead should be fairly simple, and if it's true then > having a pool of workers would be a good optimisation. > > Ross > > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- "Do or do not. There is no try" Yoda Master -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
