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