From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
bitbake-devel <bitbake-devel@lists.openembedded.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: RE: [bitbake-devel] Cache timings with various changes
Date: Wed, 23 Nov 2022 04:33:37 +0000 [thread overview]
Message-ID: <87f9939926fd4a488abb8e6442c6100a@axis.com> (raw)
In-Reply-To: <f963c6619df931162db7de468699d2aad0c1b76a.camel@linuxfoundation.org>
> -----Original Message-----
> From: bitbake-devel@lists.openembedded.org <bitbake-devel@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 23 november 2022 01:07
> To: bitbake-devel <bitbake-devel@lists.openembedded.org>
> Cc: Joshua Watt <JPEWhacker@gmail.com>
> Subject: [bitbake-devel] Cache timings with various changes
>
> I've talked about changing the data we cache in various forums. These
> are some actual numbers from a local system (88 core):
>
> Patch Full reparse time Cache load time Cache size (compressed) Cache size (uncompressed)
> ----- ----------------- --------------- ----------------------- -------------------------
> master baseline 5.732s 2.261s N/A 24M
> frozenset changes 4.326s 2.289s N/A 24M
> pickle in one 4.509s 2.177s N/A 24M
> compress with zstd 6.040s 2.204s 3.4M 24M
> add hash data to cache 9.693s 4.327s 17M 83M
>
> It seems the frozenset improvements I have speed things up nicely and
> look like a good change. The compression does slow things down, as does
> pickling the cache in one go.
>
> The patches are in poky-contrib rpurdie/t222. I'll post the frozenset
> one, the others look like they need more thought.
>
> Cheers,
>
> Richard
Not sure how you measured the times, so I just looked at the progress bars
for "Loading cache" and "Parsing recipes". With our layers (4717 recipes)
and my computer with 8 cores (16 threads), this is what I got:
* Without rpurdie/t222 applied, it takes 0-2 s to load the cache, it takes
43-46 s to parse the recipes and the cache is 185 MB.
* After applying up to "cache: Switch to compressing the cache file with
zstd", the cache load and recipe parse times remains the same, but the
size of the cache decreases to 17 MB
* With all of rpurdie/t222 applied it takes 2-3 to load the cache, 51-53 s
to parse the recipes and the cache is 55 MB.
//Peter
next prev parent reply other threads:[~2022-11-23 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 0:07 Cache timings with various changes Richard Purdie
2022-11-23 4:33 ` Peter Kjellerstedt [this message]
2022-11-23 12:24 ` [bitbake-devel] " Richard Purdie
[not found] <172A0E0769C4899C.9021@lists.openembedded.org>
2022-11-24 22:26 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87f9939926fd4a488abb8e6442c6100a@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=JPEWhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.