[bitbake-devel] [PATCH 0/2] Variable tracking: Cleaned up and rebased.
Richard Purdie
richard.purdie at linuxfoundation.org
Wed Jan 16 17:59:22 UTC 2013
On Wed, 2013-01-16 at 17:54 +0000, Richard Purdie wrote:
> I *really* want to take these, however I did want to check performance:
>
> Before:
>
> $ time bitbake core-image-sato -e
> real 0m8.034s
> $ time bitbake -p
> real 0m12.220s
> user 3m3.887s
>
> After:
>
> $ time bitbake core-image-sato -e
> real 0m50.267s
> $ time bitbake -p
> real 0m14.607s
> user 3m55.179s
>
>
> The 50s seems a touch excessive and it looks like a 20% parsing hit even
> when unused :(. Note the overall parsing times on this machine are fast
> as its running 24 in parallel. I'm going to try and figure out what is
> going on tomorrow as I've fixed a lot of this kind of thing in the past
> but wanted to mention it...
For those wanting to play:
bitbake core-image-sato -e -P
and looking at profile.log.processed shows 48 *million* calls to
deepcopy. That is a big clue to the problem.
Cheers,
Richard
More information about the bitbake-devel
mailing list