From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Yonggang Luo" <luoyonggang@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2] gitlab-ci: Decrease the size of the compiler cache
Date: Mon, 20 Oct 2025 19:56:40 +0200 [thread overview]
Message-ID: <778a093a-bc42-45fb-b466-15be9a655a05@linaro.org> (raw)
In-Reply-To: <20251020161759.50241-1-thuth@redhat.com>
On 20/10/25 18:17, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> Uploading the cache from the runner takes a long time in the MSYS2
> job, mostly due to the size of the compiler cache.
> However, looking at runs with a non-poluted cache, it seems like
> you can get a build with a 99% hit rate already with ~ 160 MiB cache
> size, so the compiler cache with 500 MiB certainly contains a lot of
> stale files. Thus decrease the size of the ccache to a more reasonable
> value to speed up the MSYS2 job in our CI.
>
> While at it, also add a "du -sh" for the build folder to get a better
> feeling for the amount of object code that is required for the build,
> and publish the list of files in /var/cache to be able to better
> analyze what is really clogging our cache here.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Decrease cache size to 180M and save cache-log.txt as artifact
>
> .gitlab-ci.d/windows.yml | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2025-10-20 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 16:17 [PATCH v2] gitlab-ci: Decrease the size of the compiler cache Thomas Huth
2025-10-20 17:37 ` Daniel P. Berrangé
2025-10-20 17:56 ` Philippe Mathieu-Daudé [this message]
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=778a093a-bc42-45fb-b466-15be9a655a05@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).